From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sourceware.org
Subject: Re: Memleaks?
Date: Mon, 30 Oct 2006 20:37:00 -0000 [thread overview]
Message-ID: <1162240667.9408.28.camel@localhost.localdomain> (raw)
In-Reply-To: <5.2.0.9.1.20061030165930.01856ec0@NT_SERVER>
On Mon, 2006-10-30 at 17:01 +0100, Fabian Cenedese wrote:
> At 08:45 30.10.2006 -0500, Daniel Jacobowitz wrote:
> >On Mon, Oct 30, 2006 at 12:40:56PM +0100, Fabian Cenedese wrote:
> >> I admit that I used not a state-of-the-art gdb, but I don't think that
> >> this was changed recently. I'd be pleased if you can correct me.
> >>
> >> GNU gdb 6.2.50_2004-10-14-cvs
> >
> >This is two years old; I can't really speculate on what has changed
> >since then. It may be simple memory leaks, or it may be something more
> >complex.
>
> Actually 6.5 behaves the same as 6.2.5. The difference was not the
> version but the calling. When started with "gdb --readnow" every file
> read will leave some memory behind and use more and more. So it
> seems that the full symbols are not cleaned up as well as the partial
> symbols.
It's not at all surprising that that would make a difference.
With --readnow, you're going to do an enormous amount of mallocing.
next prev parent reply other threads:[~2006-10-30 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 11:41 Memleaks? Fabian Cenedese
2006-10-30 13:45 ` Memleaks? Daniel Jacobowitz
2006-10-30 15:06 ` Memleaks? Fabian Cenedese
2006-10-30 15:08 ` Memleaks? Daniel Jacobowitz
2006-10-30 16:02 ` Memleaks? Fabian Cenedese
2006-10-30 20:37 ` Michael Snyder [this message]
2006-10-31 7:27 ` Memleaks? Fabian Cenedese
2006-10-31 12:16 ` Memleaks? Christopher Faylor
2006-11-02 7:31 ` *SPAM*Re: Memleaks? Fabian Cenedese
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=1162240667.9408.28.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=Cenedese@indel.ch \
--cc=gdb@sourceware.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