From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23387 invoked by alias); 23 Sep 2010 16:06:58 -0000 Received: (qmail 23368 invoked by uid 22791); 23 Sep 2010 16:06:55 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,MIME_QP_LONG_LINE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp2.peak6.com (HELO smtp2.peak6.com) (38.98.137.9) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Sep 2010 16:06:46 +0000 From: Richard Hedin To: 'Jan Kratochvil' CC: "'gdb@sourceware.org'" Date: Thu, 23 Sep 2010 16:06:00 -0000 Subject: RE: heap info Message-ID: <59803715F2379947A4B8AFDBB4596B02126DB3@spswchi6mail1.peak6.net> References: <59803715F2379947A4B8AFDBB4596B02126DAC@spswchi6mail1.peak6.net> <20100923152453.GA5925@host1.dyn.jankratochvil.net> In-Reply-To: <20100923152453.GA5925@host1.dyn.jankratochvil.net> Content-Type: text/plain; charset="us-ascii" content-transfer-encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-09/txt/msg00120.txt.bz2 Hi, Jan. I'm trying to use valgrind --tool=3Dmassif. 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=3Dmassif. It's pa= infully 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 limi= t. Try: valgrind --tool=3Dmassif ./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