On Mon, 24 Oct 2011 16:01:30 -0700, Ben Kennedy <b...@zygoat.ca> said: >On 24 Oct 2011, at 3:53 pm, Matt Neuburg wrote: > >> That's all! Dude, where's my reason? And without a printing of the reason, >> what's the good of the assert? (And hey, I wouldn't mind seeing that lovely >> call stack, too.) > >Exceptions don't get logged automatically anymore when running under iOS 5, in >my experience. I've had to manually add breakpoint actions of "po $eax" and >"po $r0" on "objc_exception_throw" and "-[NSException raise]" to deal with >this problem.
Thanks, I'll give it a shot. It seems to be an Xcode thing rather than an iOS 5 thing; I say this because if I run the same app in a debug build and hit the same NSAssert, not within Xcode but independently on the device or in the simulator, the NSAssert reason and stack trace *are* printed. So I'm guessing that Xcode is being a smartypants and somehow jumping in and suppressing the additional logging. m. -- matt neuburg, phd = m...@tidbits.com, <http://www.apeth.net/matt/> A fool + a tool + an autorelease pool = cool! Programming iOS 4! http://www.apeth.net/matt/default.html#iosbook_______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
