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" <scott_r...@killerbytes.com> To: "Paul Sanders" <p.sand...@alpinesoft.co.uk>; "Dave Camp" <d...@thinbits.com>; "Cocoa Dev" <cocoa-dev@lists.apple.com> 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 (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
