This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Memory Dump
- From: Hei Chan <structurechart at yahoo dot com>
- To: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>, xgsa <xgsa at yandex dot ru>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Sat, 5 May 2012 17:55:07 -0700 (PDT)
- Subject: Re: Memory Dump
- References: <1335710405.38804.YahooMailNeo@web162403.mail.bf1.yahoo.com> <4FA22BFD.1060600@yandex.ru> <A74F579037814D50BB276EABABD76BB1@soleil>
- Reply-to: Hei Chan <structurechart at yahoo dot com>
Hi Phillippe,
The feature you mentioned sounds interesting.
Is it capable of taking heap snapshot per user request/command?
What's the name of that feature? ?I want to look it up. ? Or do you have a link? ?(don't see it in the release note of Valgrind 3.7.0).
Thanks in advance.
Cheers,
Hei
----- Original Message -----
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: xgsa <xgsa@yandex.ru>; Hei Chan <structurechart@yahoo.com>
Cc: gdb@sourceware.org
Sent: Thursday, May 3, 2012 12:22 PM
Subject: Re: Memory Dump
> 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