Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: How to debug *** -[NSCFString count]: unrecognized selector sent to instance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to debug *** -[NSCFString count]: unrecognized selector sent to instance

Subject: Re: How to debug *** -[NSCFString count]: unrecognized selector sent to instance
From: Joar Wingfors <email@hidden>
Date: Fri, 17 Apr 2009 07:25:35 -0700


On 17 apr 2009, at 07.16, Marc Stibane wrote:

Any tips how I could find out which object the system wanted to send the message to in the first place?

Are there any debugging tools which e.g. mark (auto-)released objects as dead, but do not free their memory so that new allocations cannot take the same space? Then I could identify the original object...

Yes, and that facility is known as NSZombieEnabled:

<http://www.google.com/search?q=site:developer.apple.com+NSZombieEnabled >

j o a r


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: How to debug *** -[NSCFString count]: unrecognized selector	sent to instance
From: "Jeremy W. Sherman" <email@hidden>
Re: How to debug *** -[NSCFString count]: unrecognized selector	sent to instance
From: Marc Stibane <email@hidden>


References:  
  >How to debug *** -[NSCFString count]: unrecognized selector sent to	instance (From: Marc Stibane <email@hidden>)




Prev by Date:
How to debug *** -[NSCFString count]: unrecognized selector sent to	instance

Next by Date:
Basic file operation question

Previous by thread:
How to debug *** -[NSCFString count]: unrecognized selector sent to	instance

Next by thread:
Re: How to debug *** -[NSCFString count]: unrecognized selector	sent to instance

Index(es):

Date
Thread