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 13:38:25 -0400
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