Article View: gnu.gcc.help
Article #49583Re: debugging malloc for gcc?
From: Scott Schwartz
Date: Sat, 08 Jan 1994 03:14
Date: Sat, 08 Jan 1994 03:14
11 lines
1185 bytes
1185 bytes
pcc@control.ca.sandia.gov (Phil Cox) writes: I am actually looking for something like purify, except less expensive :-). Any /All pointers would be appreciated. Check out Hans Boehm's gc_malloc, which you can ftp from parcftp.xerox.com:pub/russell/gc3.5.tar.Z. gc_malloc is a garbage collecting malloc--free is a no-op. By it's very nature you eliminate a whole class of common errors. If you turn on all the debugging switches, it can detect and report memory leaks and other problems.
Technical Details
Message-ID:
<SCHWARTZ.94Jan7221403@roke.cse.psu.edu>Path:
arc1-ca.pugleaf.net!gmd.de!xlink.net!howland.reston.ans.net!gatech!psuvax1!psuvax1.cse.psu.edu!schwartzReferences:
<2gkt5p$24i@control.ca.sandia.gov>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,bc3f2d37f621cb30 X-Google-Attributes: gid11318c,public X-Google-ArrivalTime: 1994-01-07 20:56:22 PST Newsgroups: gnu.gcc.help Path: arc1-ca.pugleaf.net!gmd.de!xlink.net!howland.reston.ans.net!gatech!psuvax1!psuvax1.cse.psu.edu!schwartz From: schwartz@roke.cse.psu.edu (Scott Schwartz) Subject: Re: debugging malloc for gcc? In-Reply-To: pcc@control.ca.sandia.gov's message of 7 Jan 1994 16:02:01 -0800 Message-ID: <SCHWARTZ.94Jan7221403@roke.cse.psu.edu> Sender: news@cse.psu.edu (Usenet) Nntp-Posting-Host: roke.cse.psu.edu References: <2gkt5p$24i@control.ca.sandia.gov> Date: Sat, 8 Jan 1994 03:14:03 GMT Lines: 12