Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Hedin <rhedin@peak6.com>
To: 'Jan Kratochvil' <jan.kratochvil@redhat.com>
Cc: "'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: RE: heap info
Date: Thu, 23 Sep 2010 16:06:00 -0000	[thread overview]
Message-ID: <59803715F2379947A4B8AFDBB4596B02126DB3@spswchi6mail1.peak6.net> (raw)
In-Reply-To: <20100923152453.GA5925@host1.dyn.jankratochvil.net>

Hi, Jan.

I'm trying to use valgrind --tool=massif.  Thanks for the idea.

I am working with a core file.  As far as I know, valgrind doesn't handle a core file.

I am running the application again under valgrind --tool=massif.  It's painfully slow, and I'm not sure I can get results.

Any techniques to work on a dead core file?  Some kind of post-mortem heap walker?



                   Regards,

                   Rick

-----Original Message-----
From: Jan Kratochvil [mailto:jan.kratochvil@redhat.com]
Sent: Thursday, September 23, 2010 10:25 AM
To: Richard Hedin
Cc: 'gdb@sourceware.org'
Subject: Re: heap info

On Thu, 23 Sep 2010 16:09:56 +0200, Richard Hedin wrote:
> I need to find out which object in my application is growing without limit.

Try: valgrind --tool=massif ./app

valgrind also has various options for the allocations reporting.


Regards,
Jan

______________________________________________

See  http://www.peak6.com/email_disclaimer.php
for terms and conditions related to this email


  reply	other threads:[~2010-09-23 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 14:10 Richard Hedin
2010-09-23 15:25 ` Jan Kratochvil
2010-09-23 16:06   ` Richard Hedin [this message]
2010-09-23 16:29     ` Jan Kratochvil
2010-09-23 17:00 ` Michael Snyder
2010-09-24  1:43 ` 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=59803715F2379947A4B8AFDBB4596B02126DB3@spswchi6mail1.peak6.net \
    --to=rhedin@peak6.com \
    --cc=gdb@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