12-08-2011 01:58 AM - edited 12-08-2011 01:59 AM
What's the approach I should take when trying to locate a bug that never seems to show up when the debugger is attached? I have no idea what could be the cause of the bug.
I am trying to debug via the device. My simulator isn't working (another issue) so I can't debug with that.
12-12-2011 11:49 AM
Are you using the same build of the application for either test?
What OS version is running on your PlayBook?
12-12-2011 04:13 PM
Yes, I am positive that I am testing with the same build of my application. My device is using 184.108.40.20667, and it was exhibiting this behaviour with the previous major update as well. I only just downloaded 220.127.116.1167 so I couldn't yet say this issue has occurred with this version, but I am currently doing testing on this. I will report back.
12-12-2011 04:22 PM
The diffrence between debug and release variants are
- release variant does not have debug symbols
- release variant compiled with more security features (such as PIE)
- app runs with lower privileges (for example it cannot modify its own assets)
- app assets are signed (but it should not affect app after it launched)
Did you try to run Memory analysis tool to see if it can dind any memory corruption issues?
12-12-2011 04:57 PM
I actually noticed this issue happening with the debug build, but the application wouldn't freeze if I had actually run the debugger on it. I haven't actually seen any problems in the release build of my application, which is a good thing, but I'm still worried about what I saw with the debug build.
I am not great with the MAT but I will use it and report back.