09-11-2013 04:30 PM
My previously stable app has started to crash ramdomly with SIGSEGV faults, which are usually due to trying to write to the target of a bad pointer. The crashes are happening on my Z10 development device, and I have the .core file dumped in the sandbox and I'm trying to do a postmortem debug, but I just can't get a stack trace from Momentics. As per this page I copied the .core file to my project workspace and created a new debug launch configuration that points to it. Although it isn't mentioned on that page, this also requires you to set the C/C++ application, which I pointed to the compiled arm version. When I hit Debug it shows up in the debug perspective, and I can expand it one level, but that's as far as I get. No stack trace is shown and I can't figure out how to do anything with it. Has anyone got this working?
This is as far as I get:
09-12-2013 12:11 AM - edited 09-12-2013 12:14 AM
That's very strange. I did not set them as private, and when I try to edit the post I can 't see any indication that they are private, so I don't know how to change it.
UPDATE: May have just been a temporary site glitch, or perhaps you have your browser set to block images. I just tried signing out and viewing the thread and I can see the images fine.
09-12-2013 05:34 AM - edited 09-12-2013 05:36 AM
09-12-2013 06:12 AM
It works for me. Are you on 10.2?
If so try this way;
1) Right click on your project, select Debug as->Debug Configurations...
2) Select BlackBerry Postmortem Debugging from the left hand list
3) Click on the new icon at the top-left of the list
4) You should find there is only a Core file text field in the dialog window that appears
5) Browse to your core file and select
6) Click on the Apply button followed by the Debug button
7) A 'Confirm Perspective Switch' dialog should come up, click on yes and you should be good to go
I of course never use it as my code never crashes. [Coughs]
Good luck tracking the problem down.
09-12-2013 07:12 PM
No not yet, I'm still on 10.1, I'm leery of upgrading my toolchain in between releases. After my next release goes out I will probably upgrade then. I was likely spooked by my 10.0 to 10.1 experience, which was atrocious. I had huge numbers of libraries that were included automatically by the 10.0 new app template (and which I didn't notice and didn't need) that were no longer available in the 10.1 SDK. Many hours of hand editing of obscure files followed before my app would compile again.
As for your instructions, that is exactly what I did in 10.1, but of course it also asked for the app as the first image shows, and I never get the "confirm perspective switch" message. It just goes straight to what you see in the first image.
09-13-2013 06:40 AM
09-13-2013 09:58 AM
Yes, I'm having to bite the bullet and install 10.2 on another machine. I'm beginning to suspect this is a Cascades problem though, not my code. I've been through it with a fine-toothed comb and I'm not allocating or releasing memory anywhere near the places where it crashes. I refactored to remove the one place where i was creating and destroying objects and I thought that fixed it, but this morning it crashed again so it's back to the drawing board.
09-13-2013 10:02 AM