Yep, I hit continue. It just jumps to __kill without logging. Printing the first argument might work, I'll try that next time.
Sent from my iPhone On Jan 29, 2012, at 8:54, Kyle Sluder <kyle.slu...@gmail.com> wrote: > On Jan 29, 2012, at 3:55 AM, Rick Mann <rm...@latencyzero.com> wrote: > >> Figured it out. Some of the objects in my new nib weren't properly set up. >> >> In this day and age of Xcode 4 and iOS 5, I'm really disappointed that the >> NIB loading still doesn't report errors very well. > > When it threw an exception, did you break in the debugger? By default, Xcode > breaks on objc_exception_throw. Obviously you will need to hit Continue if > you want to see any log output. Or you could just print the first argument; > consult your local ABI documentation for more info. > > --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
