The joy of unexpected SIGABRTs
The joy of unexpected SIGABRTs
- Subject: The joy of unexpected SIGABRTs
- From: Alex Zavatone <email@hidden>
- Date: Sat, 29 Sep 2012 00:00:39 -0400
I'm trying to get a rather important demo together and plan on being up all night again, so pleas pardon me if my brain power appears lacking.
About 10 mins ago, before I started wiring up my GUI by simply dragging storyboard items into the .h file to make IBOutlets my app ran and displayed fine.
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.
Nothing.
This is what drives me insane about Xcode.
So, I commented out all the code I just added and still, BLAM, directly when the scene loads. Even the breakpoint for the Init method isn't getting triggered.
So, obviously, this is a storyboard issue, but which, but what?
Considering that Xcode displays nothing at all that actually indicates what caused the SIGABRT, if it is thrown from a storyboard, what tips do you have to help track these unpleantries down when they are triggered form the storyboard?
Trapping for -[NSObject(NSObject) doesNotRecognizeSelector:]
doesn't help.
Thanks in advance.
_______________________________________________
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