On Wed, Feb 22, 2012 at 7:53 AM, R <r4eem...@gmail.com> wrote: > and now see: > > Catchpoint 2 (throw)Pending breakpoint 1 - "objc_exception_throw" > resolved > > > No further details. The app appears to be fine with no errors or > warnings. Is this a problem? > > (SnowLeopard Xcode 4)
This the result of some non-obvious changes made between Xcode 3 and Xcode 4. 1. "Break on Objective-C exceptions" is on by default, which will cause the debugger to break on objc_exception_throw. 2. "Show Disassembly When Debugging" is off by default, meaning that when you break in the debugger Xcode will select the first frame on the stack that contains _your_ code; often times this is the call to NSApplicationMain(). The frequency of this question leads me to believe the defaults are confusing and should be changed. But for now, the upshot is that you can hit Continue and let the exception remain uncaught and logged to the console, or you can examine the exception object directly using gdb (`po $rsi` on 64-bit Intel). --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
