10-27-2013 10:37 AM
You have a trace statement as the first executable line in your app's main class constructor (to verify that execution is getting handed off to your app)?
Can you verify directly in your bar manifest that the entry point type is indeed qnx air debug and not just qnx air?
This is a shot in the dark but if you pull up the core file in a hex editor and/or dump strings with e.g. the "strings" *nix utility, is there anything in there that looks vaguely like a stack trace?
10-27-2013 11:32 AM
10-27-2013 11:39 AM
Hope you have a good audit trail to get back to original state.
Frustrating to not be able to reproduce problems reported in the wild.
A big reason why I believe in having a version controlled commandline build flow.
I'm posting in quasi-haiku now.
Need more coffee.
10-27-2013 11:41 AM
10-27-2013 06:48 PM
10-29-2013 07:47 AM
10-29-2013 08:26 AM
Just curious, were you able to glean that from your core file, or did you interpolate it from new trace statements you inserted into your code?
In the googling that I did earlier on this thread, I wasn't able to find any info on how to actually interpret the adl.core file, whether/how it could be pulled into a debug session, etc.
10-29-2013 09:56 AM
10-29-2013 12:10 PM