Re: troubleshooting unrecognised selector messages
Re: troubleshooting unrecognised selector messages
- Subject: Re: troubleshooting unrecognised selector messages
- From: Thomas Engelmeier <email@hidden>
- Date: Mon, 12 Nov 2007 09:58:10 +0100
On 07.11.2007, at 22:21, Andrew Ebling wrote:
2007-11-07 21:15:35.692 RaiseMan[543:10b] *** -[NSCFNumber <null
selector>]: unrecognized selector sent to instance 0x110e50
Any ideas how to go about troubleshooting these sorts of messages?
I tried poking around with gdb on the command line to see if I could
find out what was sitting at the supplied address, without success.
The easiest way to debug such behavior is to provide the unrecognized
method in a category and set a breakpoint there.
A little more effort is to add a category for -
(void)doesNotRecognizeSelector:(SEL)aSelector, either for the
concretete class that throws or up in the class hierachy to NSObject.
Just make sure either version is not present in release builds.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden