Best way to track down a double-delete
Best way to track down a double-delete
- Subject: Best way to track down a double-delete
- From: "John Cebasek" <email@hidden>
- Date: Wed, 8 Mar 2006 09:10:45 -0500
Hi All:
I'm debugging a secuity agent plugin and I've run into a snag that causes a delete to be sent to an un-initialized variable or to the same variable twice. So there's the call stack that ends with objc_msgSend(). Here's the bt from the crash:
objc_msgSend()
??
__NSFireMachPort()
__CFMachPortPerform()
CFRunLoopRunSpecific()
CFRunLoopRunInMode()
RunCurrentEventLoopInMode()
ReceiveNextEventCommon()
BlockUntilNextEventMatchingListInMode()
_DPNextEvent()
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?
Any pointers would be appreciated
John Cebasek
_______________________________________________
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