Re: Best way to track down a double-delete
Re: Best way to track down a double-delete
- Subject: Re: Best way to track down a double-delete
- From: "John Cebasek" <email@hidden>
- Date: Wed, 8 Mar 2006 16:57:24 -0500
Hi Nick:
Thanks for the hint, but it doesn't seem to be displaying any info
differently than without. I have to break into my plugin at a known point
with some code like:
volatile int nLoop = 1;
while (nLoop)
{
sleep(1);
}
and in GDB set nLoop to zero and then continue.
If I set NSZombieEnabled to yes before I set nLoop to zero, that's not going
to help because security agent has already started up and queried any
environment variables, right?
Am I doing something wrong?
Any other hints?
John
----- Original Message -----
From: "Nick Zitzmann" <email@hidden>
To: "John Cebasek" <email@hidden>
Cc: <email@hidden>
Sent: Wednesday, March 08, 2006 9:28 AM
Subject: Re: Best way to track down a double-delete
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