XCode 4.2 : when app crashes, threads rarely display callstack

Question

Since I've installed the last xCode (my previous one was the 3.xx), a have hard times to debug my crashing apps. Indeed, the callstack is often empty. And the displayed method is

int main(int argc, char *argv[]) {   
    NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];
    int retVal = UIApplicationMain(argc, argv, nil, @"MyAppDelegate");
    [pool drain];
    return retVal;
}

Ex : Empty call stack !

Have anyone noticed this ? It was working perfectly on the same project with previous XCode. Is there any solution ?

Check this out - http://stackoverflow.com/questions/1373858/easy-way-to-print-current-stack-trace-of-an-app/5037433#5037433 — rishi, Feb 13 '12 at 16:46
And check out http://stackoverflow.com/questions/8100054/no-exception-stack-trace-in-console-under-xcode-4-2-ios-5 — Hot Licks, Feb 13 '12 at 16:56

score 9 · Accepted Answer · answered Feb 13 '12 at 19:07

9

Try setting Exception Breakpoint on Breakpoint panel:

enter image description here

answered Feb 13 '12 at 19:07

iHunter

6,205
3
38
56

Wow ! It works for this crash. Thanks for the magic trick, but it seems too simple after reading the links above... – Martin Feb 14 '12 at 09:04

score 3 · Answer 2 · answered Feb 13 '12 at 18:12

3

Notice that you can change the number of items displayed in the stack frames view by dragging the slider at the bottom of the view.

answered Feb 13 '12 at 18:12

rooftop

3,031
1
22
33

1

cooool ! I never noticed it before – Martin Feb 14 '12 at 08:57

XCode 4.2 : when app crashes, threads rarely display callstack

2 Answers2