This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Memory Leaks
- To: help-gcc at gnu dot org
- Subject: Re: Memory Leaks
- From: phil+s3 at bolthole dot no-bots dot com (Philip Brown)
- Date: 26 Nov 1999 17:20:23 GMT
- Newsgroups: gnu.gcc.help
- Organization: Phil's Software
- References: <383536D0.C1DA51E8@cable.A2000.nl> <rmcc18.vu6.ln@127.0.0.1>
- Reply-To: phil+s3 at bolthole dot no-bots dot com
- Xref: wodc7nx0 gnu.gcc.help:1973
On Mon, 22 Nov 1999 22:31:07 +0200, jhm@cistron.nl wrote:
>Fred Wan <a.wan@cable.A2000.nl> wrote:
>>Does anyone know if there are possibilities of tracing memory leaks with
>>gdb (xxgdb)?
>
>There are numerous tools that can be used with gcc + gdb; see
>http://www.cs.colorado.edu/homes/zorn/public_html/MallocDebug.html . There's
>even a gcc modified for leak tracking called "Checker" (I think it has a
>homepage on www.gnu.org), but I don't know how mature it is.
fairly UNmature.
For example, you can't even use it on X executables.
--
[Trim the no-bots from my address to reply to me by email!]
[ Do NOT email-CC me on posts. Pick one or the other.]
http://thomas.loc.gov/cgi-bin/bdquery/z?d105:SN01618:@@@D
The word of the day is mispergitude