Re: NSExtraMIData?
Re: NSExtraMIData?
- Subject: Re: NSExtraMIData?
- From: "Sean McBride" <email@hidden>
- Date: Tue, 12 Jan 2010 16:52:17 -0500
- Organization: Rogue Research Inc.
I guess when dealing with Obj-C objects, NSZombieEnabled=YES together
with NSDeallocateZombies=NO does #2 and sorta does #3.
But, as I said, I was wondering if there is a way to extend this to all
allocations (ie non-objects). Additionally, NSZombieEnabled does
nothing under GC, and I'd be interesting in knowing if there is
something similar for that case.
On 1/12/10 9:37 PM, Mike Abdullah said:
>Turn on NSZombieEnabled.
>
>On 12 Jan 2010, at 18:51, Sean McBride wrote:
>
>> On 1/11/10 8:10 PM, Greg Parker said:
>>
>>> Most likely, you over-released some other object and then an
>>> NSExtraMIData was allocated at the same address. When you later try to
>>> use the dead over-released object, the message is sent to the
>>> NSExtraMIData object.
>>
>> Greg,
>>
>> Is there any way to prevent future objects from being allocated at a
>> previously used address? It seems that would help debug such things.
>>
>> Even more generally, can free() be made to:
>> 1) scribble the passed buffer (MallocScribble)
>> 2) leak the buffer
>> 3) mark the associated pages as no access
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden