From: Erik de Castro Lopo <erikd@zip.com.au>
To: help-gcc@gnu.org
Subject: Re: Memory Leaks
Date: Fri, 19 Nov 1999 13:02:00 -0000 [thread overview]
Message-ID: <3835B576.7E54C734@zip.com.au> (raw)
In-Reply-To: <38354BAD.3BAD769B@cable.A2000.nl>
Fred Wan wrote:
>
> Hi,
>
> Does anyone know if there are possibilities of tracing memory leaks with
>
> gdb (xxxgdb)? The only thing I now have at my disposal is Visual C++,
> and
> its routines for tracing those kinds of errors are insufficient and
> inaccurate (but what can you expect from microsoft?). I was used to the
> commercial C++ compiler package from IBM on a RISC\6000 AIX machine,
> that includes a heap debugger, an excellent program. I now have Solaris
> 7 (on intel) with just g++ and gdb and I haven't found any specialized
> ways of tracking memory leaks.
Have a look at this page:
http://www.cs.colorado.edu/homes/zorn/public_html/MallocDebug.html
Erik
--
+-------------------------------------------------+
Erik de Castro Lopo erikd@zip.com.au
+-------------------------------------------------+
Spook bait:
heroin Albright terrify extradite packages uranium
airport terminal Yeltsin code kill blast president
train station Clinton opium nitro money sneak hash
keep secret DEA smuggle FBI get caught execute LSD
assassinate NSA terrorize bombed encrypt plutonium
WARNING: multiple messages have this Message-ID
From: Erik de Castro Lopo <erikd@zip.com.au>
To: help-gcc@gnu.org
Subject: Re: Memory Leaks
Date: Tue, 30 Nov 1999 23:28:00 -0000 [thread overview]
Message-ID: <3835B576.7E54C734@zip.com.au> (raw)
Message-ID: <19991130232800.tEEIW79SPEnGZnfwVnt5aefbWgeqVZaoraNeSfUe3Uo@z> (raw)
In-Reply-To: <38354BAD.3BAD769B@cable.A2000.nl>
Fred Wan wrote:
>
> Hi,
>
> Does anyone know if there are possibilities of tracing memory leaks with
>
> gdb (xxxgdb)? The only thing I now have at my disposal is Visual C++,
> and
> its routines for tracing those kinds of errors are insufficient and
> inaccurate (but what can you expect from microsoft?). I was used to the
> commercial C++ compiler package from IBM on a RISC\6000 AIX machine,
> that includes a heap debugger, an excellent program. I now have Solaris
> 7 (on intel) with just g++ and gdb and I haven't found any specialized
> ways of tracking memory leaks.
Have a look at this page:
http://www.cs.colorado.edu/homes/zorn/public_html/MallocDebug.html
Erik
--
+-------------------------------------------------+
Erik de Castro Lopo erikd@zip.com.au
+-------------------------------------------------+
Spook bait:
heroin Albright terrify extradite packages uranium
airport terminal Yeltsin code kill blast president
train station Clinton opium nitro money sneak hash
keep secret DEA smuggle FBI get caught execute LSD
assassinate NSA terrorize bombed encrypt plutonium
next prev parent reply other threads:[~1999-11-19 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-19 5:09 Fred Wan
1999-11-19 13:02 ` Erik de Castro Lopo [this message]
1999-11-30 23:28 ` Erik de Castro Lopo
1999-11-30 23:28 ` Fred Wan
[not found] <383536D0.C1DA51E8@cable.A2000.nl>
[not found] ` <rmcc18.vu6.ln@127.0.0.1>
1999-11-26 9:30 ` Philip Brown
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
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=3835B576.7E54C734@zip.com.au \
--to=erikd@zip.com.au \
--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).