Re: debugging unrecognized selector

2014-05-16 Thread ChanMaxthon
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  wrote:
> 
> 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'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

Re: debugging unrecognized selector

2014-05-16 Thread Kyle Sluder
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'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/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: debugging unrecognized selector

2014-05-16 Thread Torsten Curdt
> 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 doesn’t have such a method, so the
> breakpoints will never trigger. (You’ve effectively set a breakpoint on a
> global symbol that doesn’t exist.)

Ah, OK I thought it wouldn't matter whether the selector exists for
the debugger to catch it.

Thanks, guys!

___

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

Re: debugging unrecognized selector

2014-05-16 Thread Quincey Morris
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-16 09:46:56.796 MyApp[30998:60b] -[__NSCFString CGColor]:
> unrecognized selector sent to instance 0x10debb640
> 
> Checking the address with `po` I can see the string. But it still did
> not help to find where this happens. I added the following
> breakpoints:
> 
> * All Exceptions
> * -[__NSCFString CGColor]
> * -[NSString CGColor]

The last 2 won’t help. NSString doesn’t have such a method, so the breakpoints 
will never trigger. (You’ve effectively set a breakpoint on a global symbol 
that doesn’t exist.)

___

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

Re: debugging unrecognized selector

2014-05-16 Thread ChanMaxthon
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 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 instance 0x10debb640
> 
> Checking the address with `po` I can see the string. But it still did
> not help to find where this happens. I added the following
> breakpoints:
> 
> * All Exceptions
> * -[__NSCFString CGColor]
> * -[NSString CGColor]
> 
> but the CGColor breakpoints are not catching this. Why not?
> How would you track this down?
> 
> 
> I hope this is not too OT. If it is please let me know where to ask instead.
> 
> cheers,
> Torsten
> ___
> 
> 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