From: phil+s3@bolthole.no-bots.com (Philip Brown)
To: help-gcc@gnu.org
Subject: Re: Memory Leaks
Date: Tue, 30 Nov 1999 23:28:00 -0000 [thread overview]
Message-ID: <slrn83tgan.m3r.phil+s3@shell3.ba.best.com> (raw)
Message-ID: <19991130232800.Mv7ksNw7OhiGiyHWYRAuoZDJgM7vWvA5ZALxPJiQLjw@z> (raw)
In-Reply-To: <rmcc18.vu6.ln@127.0.0.1>
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
next parent reply other threads:[~1999-11-30 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <383536D0.C1DA51E8@cable.A2000.nl>
[not found] ` <rmcc18.vu6.ln@127.0.0.1>
1999-11-26 9:30 ` Philip Brown [this message]
1999-11-30 23:28 ` Philip Brown
1999-12-02 6:38 ` Paul Scott
1999-12-31 22:24 ` Paul Scott
1999-11-28 21:07 ` Greg Newby
1999-11-30 23:28 ` Greg Newby
1999-11-19 5:09 Fred Wan
1999-11-19 13:02 ` Erik de Castro Lopo
1999-11-30 23:28 ` Erik de Castro Lopo
1999-11-30 23:28 ` Fred Wan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrn83tgan.m3r.phil+s3@shell3.ba.best.com \
--to=phil+s3@bolthole.no-bots.com \
--cc=help-gcc@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).