Re: Suggestions for C malloc debugging tool

> Joerg Schoen wrote:
> >[instrument C source code with pointer validity checks]
>
> Let me start off by saying that I believe *anything* to decrease the
> chance of pointer errors in "C" is a good thing (assuming you must use
> C at all).


Seconded. One step in this direction is to use a garbage
collector. Might even result in faster code (see
http://www.centerline.com/people/chase/GC/GC-faq.html). A well-known
public domain plug-in replacement for malloc() is Boehm's gc (see
ftp://parcftp.xerox.com/pub/gc/gc.html). Boehm's garbage collector
can, to a certain extent, be used for finding memory leaks.




                                                                                                                          Philip Lijnzaad


--
finger lijnzaad@ebi.ac.uk for PGP public key
fingerprint: E1 03 BF 80 94 61 B6 FC 50 3D 1F 64 40 75 FB 53
--

Return to the comp.compilers page.
Search the comp.compilers archives again.