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 s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
