This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: heap info

From: Richard Hedin <rhedin at peak6 dot com>
To: 'Jan Kratochvil' <jan dot kratochvil at redhat dot com>
Cc: "'gdb at sourceware dot org'" <gdb at sourceware dot org>
Date: Thu, 23 Sep 2010 11:06:40 -0500
Subject: RE: heap info
References: <59803715F2379947A4B8AFDBB4596B02126DAC@spswchi6mail1.peak6.net> <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

Follow-Ups:
- Re: heap info
  - From: Jan Kratochvil

References:
- heap info
  - From: Richard Hedin
- Re: heap info
  - From: Jan Kratochvil

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]