I believe the intention of the slider is that it won't drop you to stack frames that does not have your code (and show you with assembler) but it can be troublesome.
When LLDB break your program at signal your program could have already progressed past where the exception happened and already popped all the way back to main(). When diagnosing selector not found you should break on [NSObject doesNotRecogniseSelector:] or [NSObject forwardInvocation:] Sent from my iPhone > On May 16, 2014, at 10:38 PM, Kyle Sluder <k...@ksluder.com> wrote: > > On May 16, 2014, at 3:07 AM, Torsten Curdt <tcu...@vafer.org> wrote: > >>> the debugger only stops in UIApplicationMain. >>> >>> That’s most likely because your “level of detail” slider (the horizontal >>> slider below the call stack in the Debug pane) isn’t at the extreme right >>> end. >> >> OMG! There is slider!? That's a revelation. Thanks! > > Yet another bitten by this. You should file a bug—this slider apparently > trips up *everyone*. > > --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/xcvista%40me.com > > This email sent to xcvi...@me.com _______________________________________________ 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
