On Mar 16, 2011, at 10:31 AM, James Maxwell wrote: > I wasn't sure how to enable Guard Malloc in Xcode 4, so I just ran it with > the Allocations Instrument. Lo and behold, it doesn't crash. This didn't make > much sense to me, so I tried running the release build, rather than the debug > build. No crash. Switch back to debug.... boom.
Memory smashers can be wildly variable. Perhaps the bug is an uninitialized variable that has a different value in debug vs release. Perhaps the memory overrun happens to corrupt a different area of memory that doesn't cause a crash (or at least doesn't cause a crash yet). In any case the bug may still be there, waiting to crash or corrupt customer data when you least expect it. -- Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ 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
