This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Memory Dump
- From: "Philippe Waroquiers" <philippe dot waroquiers at skynet dot be>
- To: "xgsa" <xgsa at yandex dot ru>, "Hei Chan" <structurechart at yahoo dot com>
- Cc: <gdb at sourceware dot org>
- Date: Thu, 3 May 2012 21:22:58 +0200
- Subject: Re: Memory Dump
- References: <1335710405.38804.YahooMailNeo@web162403.mail.bf1.yahoo.com> <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