07-10-2013 01:55 PM
I am building a native BB10 application and sometimes it crashes. The logging doesn't seem to provide any helpful information since there is little consistency to what code is running when the app crashes. What can I do to track this down?
I read on a forum here that there might be a core dump file but where would I find that on the device and how would I use it? Is there a callback I can register that would get called on an interrupt when a crash is occurring so I can stop in the debugger and look at the state? Any suggestions are appreciated!
07-11-2013 02:15 PM
Run you app using Momentics NDK 'built in' debugger and once your app crashes the app will be stopped and you'll see stack trace of function calls -> you'll see where it crashed.
07-11-2013 02:30 PM - edited 07-11-2013 02:30 PM
Thanks for the info but...
1) usually (if not always?) when I get a crash in the debugger the stack trace where the crash occurred is gone and instead I am sitting at a stack trace for the signal (i.e. SIGSEGV Segmentation fault) and there is no useful data I can get here
2) often the crash occurs when I'm not debugging (i.e. on a QA device or on a Beta testers device) so it would be great to be able to look at a core dump for these cases since we often don't have steps for reproducing the issue, and even if Idid I'd be stuck at (1) above
07-12-2013 06:27 PM
I found a "core" file for a crashing QNX debugged app in "/accounts/1000/appdata/com.CounterPath.Bria.testD
07-16-2013 04:39 AM
There's a good presentation here on "Performance and Debugging for Native Developers" which describes how to examine core files amongst other things: