From: "Philippe Waroquiers" <philippe.waroquiers@skynet.be>
To: "xgsa" <xgsa@yandex.ru>, "Hei Chan" <structurechart@yahoo.com>
Cc: <gdb@sourceware.org>
Subject: Re: Memory Dump
Date: Thu, 03 May 2012 19:23:00 -0000 [thread overview]
Message-ID: <A74F579037814D50BB276EABABD76BB1@soleil> (raw)
In-Reply-To: <4FA22BFD.1060600@yandex.ru>
> Hi,
>
> I am not sure, but it seems massif (the tool from the valgrind
> toolchain) could help you.
>
> P.S. However the question is still interesting - is there a possibility
> to solve the problem with gdb? Could someone answer it?
Valgrind massif or Valgrind memcheck are providing functionalities
to give heap information. Note that Valgrind 3.7.0 has
an integrated gdbserver, which means you can do "heap snaphots"
or "leak search" or similar on request from a gdb (or from command line).
Philippe
next prev parent reply other threads:[~2012-05-03 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 14:40 Hei Chan
2012-05-03 6:56 ` xgsa
2012-05-03 14:17 ` Aurelian Melinte
2012-05-03 19:23 ` Philippe Waroquiers [this message]
2012-05-06 0:55 ` Hei Chan
2012-05-06 7:49 ` Philippe Waroquiers
2012-05-06 0:43 ` Hei Chan
2012-05-09 20:25 ` Tom Tromey
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=A74F579037814D50BB276EABABD76BB1@soleil \
--to=philippe.waroquiers@skynet.be \
--cc=gdb@sourceware.org \
--cc=structurechart@yahoo.com \
--cc=xgsa@yandex.ru \
/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).