Re: NSAssert no longer displaying reason in console
Re: NSAssert no longer displaying reason in console
- Subject: Re: NSAssert no longer displaying reason in console
- From: Kyle Sluder <email@hidden>
- Date: Wed, 02 Nov 2011 06:39:31 -0400
On Tue, Nov 1, 2011 at 10:47 PM, Matt Neuburg <email@hidden> wrote:
> On my machine, what happens is that we SIGABRT with the editor falling into main.c and no logging of any kind in the console.
Did you drag the slider at the bottom of the Breakpoint Navigator all
the way to the right to reveal framework stack frames? A confusing
aspect of Xcode 4 is that when it breaks into the debugger, it
*always* tries to show your source code rather than disassembly of the
top stack frame. This runs counter to every debugger I've ever used,
integrated or otherwise.
> Now, *if* you set up a breakpoint on objc_exception_throw *and* you add an action to "po $eax" *and* that breakpoint is turned on *and* you are using the LLDB debugger in your scheme's debug action, and you run this project, you'll break at a reasonable spot ([self.window makeKeyAndVisible]) and you'll see in the console the delightful and helpful message, "Loaded the ViewController nib but the view outlet was not set."
I have to ask why you're printing $eax. In 32-bit apps (which the
simulator is one), arguments are passed on the stack, so the exception
should be at $ebp+8. Unless there's something about the exception ABI
that I'm not familiar with?
--Kyle Sluder
(Sent from the road)
_______________________________________________
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