Re: NSInvalidArgumentException - *** -[NSRecursiveLock length]: selector not recognized
Re: NSInvalidArgumentException - *** -[NSRecursiveLock length]: selector not recognized
- Subject: Re: NSInvalidArgumentException - *** -[NSRecursiveLock length]: selector not recognized
- From: j o a r <email@hidden>
- Date: Tue, 23 Jan 2007 16:06:37 +0100
On Jan 23, 2007, at 1:48 PM, aashish tiwari wrote:
NSInvalidArgumentException - *** -[NSRecursiveLock length]:
selector not recognized
This type of error, a message sent to the object of some Cocoa class
that doesn't implement the corresponding method, is typically caused
by a memory management error. The object that was supposed to receive
the message has been deallocated, and some other object happens to
occupy the same address.
A good way to debug such a problem is to use NSZombieEnabled. Check
Google and the list archives for more information on how to do that.
j o a r
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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