On Sat, 24 May 2003, Paul M Foster wrote:
> I've got a C program I'm writing, in which something appears to be
> stepping on something else's memory. Does anyone have _personal_
> experience with a good memory checker/malloc replacement that might
> assist in debugging what's gone errant?
I second the suggestion for valgrind, it's quite capable.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:15:53 EDT