Re: The joy of unexpected SIGABRTs
Re: The joy of unexpected SIGABRTs
- Subject: Re: The joy of unexpected SIGABRTs
- From: Alex Zavatone <email@hidden>
- Date: Mon, 01 Oct 2012 14:59:59 -0400
Hmm. At least, in Xcode 4.2, I can confirm that adding a "break on all exceptions" either on throw on on catch does nothing to provide any informative information on just what is causing the exception to happen.
Console output:
Catchpoint 3 (catch)Pending breakpoint 1 - "__cxa_begin_catch" resolved
Pending breakpoint 2 - ""MainScreen.m":48" resolved
Current language: auto; currently objective-c
Catchpoint 5 (throw)(gdb)
It's just stopped in Main, in the return statement below:
return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
Thread 1: Stopped at breakpoint 1.
I don't know if you can get anything useful from that output, but I sure can't.
However, after testing on under Xcode 4.5, at least lldb outputs more useful information in the console compared to gdb in 4.2.
Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<MainScreen 0x6a72580> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key BlackButton.'
Looks like the upgrade to Mountain Lion is my next step. Thanks man. Much more useful.
On Oct 1, 2012, at 1:38 PM, Alex Zavatone wrote:
>
> On Sep 29, 2012, at 4:58 PM, Jens Alfke wrote:
>
>>
>> On Sep 28, 2012, at 9:00 PM, Alex Zavatone <email@hidden> wrote:
>>
>>> I just spent 10 mins wiring up the GUI, did nothing else, and now when one scene appears, Xcode instantly SIGABRTs, without any information in the console or the debugger that comes close to telling why this happened.
>>
>> Well, what _did_ it show?
>>
>>> Trapping for -[NSObject(NSObject) doesNotRecognizeSelector:] doesn't help.
>>
>> That’s only going to catch one specific cause of exceptions. Didn't you set an all-exceptions breakpoint as I’ve suggested a few dozen times?
>>
>> —Jens
>
> For those who also haven't had the time. Here are the references I have for this:
>
> http://blog.manbolo.com/2012/01/23/xcode-tips-1-break-on-exceptions
> http://alwaysthecritic.typepad.com/atc/2009/06/iphone-app-debugging-stop-on-exception.html
> http://stackoverflow.com/questions/4961770/run-stop-on-objective-c-exception-in-xcode-4
>
> Thanks Jens. Fingers crossed to see if it produces any useful information on those unhelpful storyboard crashes.
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden