Re: Re: Autoreleasepool problems
Re: Re: Autoreleasepool problems
- Subject: Re: Re: Autoreleasepool problems
- From: "Shawn Erickson" <email@hidden>
- Date: Wed, 19 Jul 2006 11:41:41 -0700
On 7/19/06, Kay Roepke <email@hidden> wrote:
The problem is that the EOFToken instance shouldn't be in an
autorelease pool in the first place.
It likely isn't.
As I tried to imply... I believe someplace you are over release an
object (hints point to an instance of NSString) which is leaving a
stale pointer in the current autorelease pool (the object is getting
deallocated while still in the current autorelease pool). Then your
object happens to get allocated at the same position in memory. Then
when the autorelease pool is deallocated sending a release message to
the wrong object.
NSZombie if configured correct can be used to ensure that the same
spot in memory isn't reused allowing you to detect which object is
being over released instead of the object that just happens to be
currently allocated at the same spot in memory that once held the over
release object.
-Shawn
_______________________________________________
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