Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
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 18.104.22.16867, and it was exhibiting this behaviour with the previous major update as well. I only just downloaded 22.214.171.12467 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.