Re: NSExtraMIData?
Re: NSExtraMIData?
- Subject: Re: NSExtraMIData?
- From: Mike Abdullah <email@hidden>
- Date: Tue, 12 Jan 2010 21:37:19 +0000
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
>
> ?
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng email@hidden
> Rogue Research www.rogue-research.com
> Mac Software Developer Montréal, Québec, Canada
>
>
> _______________________________________________
>
> 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
_______________________________________________
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