Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Hei Chan <structurechart@yahoo.com>
Cc: xgsa <xgsa@yandex.ru>, "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Memory Dump
Date: Sun, 06 May 2012 07:49:00 -0000	[thread overview]
Message-ID: <1336290559.2213.14.camel@soleil> (raw)
In-Reply-To: <1336265707.19913.YahooMailNeo@web162404.mail.bf1.yahoo.com>

On Sat, 2012-05-05 at 17:55 -0700, Hei Chan wrote:
> Hi Phillippe,
> 
> The feature you mentioned sounds interesting.
> 
> Is it capable of taking heap snapshot per user request/command?
Yes. You can request a snapshot on user request,
either from the command line, or from a gdb connected to the Valgrind
gdbserver.

For gdbserver explanations, see
http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver
For massif snapshot requests, see
http://www.valgrind.org/docs/manual/ms-manual.html#ms-manual.monitor-commands

So, from a shell command line, to request a massif snapshot, you do
e.g.:
    vgdb snapshot filename_for_your_snapshot

From gdb connected to Valgrind gdbserver, you put breaks where relevant,
and then such a break is reached:
    monitor snapshot filename_for_your_snapshot

Note also that memcheck also provides on demand leak search
(including for still reachable blocks), showing the delta
with the previous leak search.

In 3.8.0 SVN (not yet released), Valgrind gdbserver+memcheck also
provides functionalities to list the still allocated blocks, and search
for "who" still points at these allocated blocks.

Philippe



  reply	other threads:[~2012-05-06  7:49 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
2012-05-06  0:55     ` Hei Chan
2012-05-06  7:49       ` Philippe Waroquiers [this message]
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=1336290559.2213.14.camel@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