From: Ming Zhang <blackmagic02881@gmail.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [BTT PATCH] Clean up all memory leaks
Date: Mon, 09 Apr 2007 15:03:02 +0000 [thread overview]
Message-ID: <1176130982.3677.61.camel@fs0004.ibrix.com> (raw)
In-Reply-To: <461A4CA0.10808@hp.com>
On Mon, 2007-04-09 at 10:24 -0400, Alan D. Brunelle wrote:
> Ensure that all allocated memory was released.
>
> Lots of minor clean up to help ensure all allocated memory is freed
> prior to exit. (Also closed a few files that were left open.)
>
> # valgrind --leak-check=yes --show-reachable=yes btt -i bp.bin -o btt
> -v
> =21322= Memcheck, a memory error detector.
> =21322= Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et
> al.
> =21322= Using LibVEX rev 1658, a library for dynamic binary
> translation.
> =21322= Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
> =21322= Using valgrind-3.2.1-Debian, a dynamic binary
> instrumentation framework.
> =21322= Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et
> al.
> =21322= For more details, rerun with: -v
> =21322=
> Sending range data to btt.dat
> Sending stats data to btt.avg
> 4581291 traces @ 10.7 Ktps in 426.578804
> seconds tree = |0|
> =21322=
> =21322= ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8
> from 1)
> =21322= malloc/free: in use at exit: 0 bytes in 0 blocks.
> =21322= malloc/free: 11,241,958 allocs, 11,241,958 frees,
> 440,381,362 bytes allocated.
> =21322= For counts of detected errors, rerun with: -v
> =21322= All heap blocks were freed -- no leaks are possible.
>
> Signed-off-by: Alan D. Brunelle <Alan.Brunelle@hp.com>
> ---
cool. really great to see this.
next prev parent reply other threads:[~2007-04-09 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 14:24 [BTT PATCH] Clean up all memory leaks Alan D. Brunelle
2007-04-09 15:03 ` Ming Zhang [this message]
2007-04-10 0:33 ` Alan D. Brunelle
2007-04-10 0:43 ` Alan D. Brunelle
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=1176130982.3677.61.camel@fs0004.ibrix.com \
--to=blackmagic02881@gmail.com \
--cc=linux-btrace@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).