Re: Still can't figure out this overrelease bug
Re: Still can't figure out this overrelease bug
- Subject: Re: Still can't figure out this overrelease bug
- From: Nick Zitzmann <email@hidden>
- Date: Fri, 10 Jun 2005 13:31:07 -0700
On Jun 10, 2005, at 11:00 AM, Theodore H. Smith wrote:
So how do I pin this overrelease bug down? Someone said these
zombies will help me figure out the class type being overreleased,
but I didn't get that class information.
In my executable pane in Xcode, I have the environment variable
"NSZombieEnabled" enabled with a value of "1".
I always enable NSZombieEnabled by setting it in code. Just import
<Foundation/NSDebug.h> in your target's main.m and then include a
line like "NSZombieEnabled = YES;" before NSApplicationMain() is
called. That works for me...
If you're still experiencing the problem, then that means that the
object that is being over-released is a toll-free bridged object e.g.
NSString, NSArray, NSDictionary, NSSet, NSNumber, etc.
NSZombieEnabled won't help you with them, unfortunately, because they
are released by using the CFRelease() function instead of being
deallocated in the usual way.
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