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 p
On May 16, 2014, at 3:07 AM, Torsten Curdt 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'
> 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!
> The last 2 won’t help. NSString do
On May 16, 2014, at 01:01 , Torsten Curdt 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.
> What I am seeing in the log is
>
> 2014-05
Strings does not have CGColor methods so it is not caught. Try break on
[NSObject doesNotRecognizeSelector:]
Sent from my iPhone
> On May 16, 2014, at 4:01 PM, Torsten Curdt wrote:
>
> I am seeing a crash in an iOS app and while I can reproduce it I am
> still struggling to find the location i
I am seeing a crash in an iOS app and while I can reproduce it I am
still struggling to find the location in my code because the debugger
only stops in UIApplicationMain. What I am seeing in the log is
2014-05-16 09:46:56.796 MyApp[30998:60b] -[__NSCFString CGColor]:
unrecognized selector sent to
