Re: How to find the memory smasher (Was: How to break on a variable change in XCode debugging)
Re: How to find the memory smasher (Was: How to break on a variable change in XCode debugging)
- Subject: Re: How to find the memory smasher (Was: How to break on a variable change in XCode debugging)
- From: Gwynne <email@hidden>
- Date: Mon, 20 Dec 2004 22:52:36 -0500
On Dec 20, 2004, at 10:12 PM, Lance Saleme wrote:
You might want to look into Electric Fence for catching the offending
code on the exact instruction it smashes a buffer.
I wish I could add more detail to the suggestion, but the engineer on
our project that tracked down this tool and incorporated it into our
product development isn't around at the moment to fill in the finer
points.
The place to start is at the author's free distribution site (see
below):
http://perens.com/FreeSoftware/ElectricFence/
I can only offer the testimonial that this tool caught some rather
elusive and extremely damaging memory problems in our 1.5 million line
code base that other tools missed.
I just took a look at this. From its description it seems to be a
slimmed-down version of libgmalloc. Does it offer anything that guard
malloc doesn't? (For the interested, Guard Malloc can be turned on in
Xcode from the Debug menu).
-- Gwynne, key to the Code
Email: email@hidden
Web: http://musicimage.plasticchicken.com/
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden