From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Follow specific symbol's DW_AT_decl_file
Date: Mon, 22 Jan 2007 00:26:00 -0000 [thread overview]
Message-ID: <20070122002611.GA1086@nevyn.them.org> (raw)
In-Reply-To: <20070121232610.GA13031@host0.dyn.jankratochvil.net>
On Mon, Jan 22, 2007 at 12:26:11AM +0100, Jan Kratochvil wrote:
> > I hadn't tried that one before. I used an old copy of glibc's memusage
> > script; massif is a bit more interesting.
>
> Thanks for the tip next time I need it. Interesting valgrind's memcheck says
> 618MB total and memusage 134MB total (55MB peak) but I did not check more.
memusage --mmap might be the difference.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-22 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 22:39 Jan Kratochvil
2007-01-21 16:55 ` Daniel Jacobowitz
2007-01-21 22:35 ` Jan Kratochvil
2007-01-21 22:56 ` Daniel Jacobowitz
2007-01-21 23:26 ` Jan Kratochvil
2007-01-22 0:26 ` Daniel Jacobowitz [this message]
2007-01-22 19:23 ` Jan Kratochvil
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=20070122002611.GA1086@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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