Re: if statement causing 32 Byte leak?
Re: if statement causing 32 Byte leak?
- Subject: Re: if statement causing 32 Byte leak?
- From: "Paul Sanders" <email@hidden>
- Date: Mon, 11 Jan 2010 16:57:18 -0000
I think what Graham originally said was true though - the
hardest over-release bugs to get to the bottom of are those
where a 'stale' reference is left behind in an autorelease pool,
only to blow up at some future point. That has certainly been
my experience at least and Graham's suggestion would trap all
such bugs at the point of last release (which, probably, is the
cause of the bug anyway).
Paul Sanders
http://www.alpinesoft.co.uk
----- Original Message -----
From: "Scott Ribe" <email@hidden>
To: "Paul Sanders" <email@hidden>; "Dave Camp"
<email@hidden>; "Cocoa Dev" <email@hidden>
Sent: Monday, January 11, 2010 4:39 PM
Subject: Re: if statement causing 32 Byte leak?
Of course none of this will get you a break on the actual error
except
occasionally when you're lucky and it's the last release (not
autorelease)
that's wrong--it merely puts the break more or less closer to
the bug than
the current NSZombie stuff.
_______________________________________________
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