Lists

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

Re: Best way to track down a double-delete

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

Re: Best way to track down a double-delete

Subject: Re: Best way to track down a double-delete
From: Nick Zitzmann <email@hidden>
Date: Wed, 8 Mar 2006 07:28:31 -0700


On Mar 8, 2006, at 7:10 AM, John Cebasek wrote:

I've been remote debugging the code and I know the error occurs when objects are being destroyed as I see various strings destructors being called, but this last one is causing a bit of grief.

Any 'best practices' on tracking a bug like this down?

Try setting the environmental variable "NSZombieEnabled" to "YES" before you run your program in the debugger. When it's in the debugger, break on -[_NSZombie methodSignatureForSelector:]. More advice here: <http://developer.apple.com/technotes/tn2004/tn2124.html>

Nick Zitzmann
<http://www.chronosnet.com/>


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


Follow-Ups:

Re: Best way to track down a double-delete
From: "John Cebasek" <email@hidden>


References:  
  >Best way to track down a double-delete (From: "John Cebasek" <email@hidden>)




Prev by Date:
Best way to track down a double-delete

Next by Date:
Broken change dictionaries in observeValueForKeyPath?

Previous by thread:
Best way to track down a double-delete

Next by thread:
Re: Best way to track down a double-delete

Index(es):

Date
Thread