[BusyBox] How to test for memory leak?

[Gregg C Levine]

Hello from Gregg C Levine
Erik, weren't you at wit's end regarding one of the memory management tools,
and its author? Or was it a debugger? Something about how it would work, or
would not work, with Busy Box, and a few of the other things, that you've
built. But any way, that's good news.
Gregg C Levine drwho8 at worldnet.att.net
"Oh my!" The Second Doctor's nearly favorite phrase.
This message made from recycled Cybermen components. 100% used Cybermen
parts.
----- Original Message -----
From: "Erik Andersen" <andersen at codepoet.org>
To: "Matthew Bloch" <matthew at bytemark.co.uk>
Cc: <busybox at busybox.net>
Sent: Monday, November 11, 2002 12:03 AM
Subject: Re: [BusyBox] How to test for memory leak?


> On Mon Nov 04, 2002 at 11:30:32PM +0000, Matthew Bloch wrote:
> > On Monday 04 November 2002 19:59, Glenn R.Heard Jr. wrote:
> > > How do you go about testing a program for a memory leak?
> >
> > Valgrind will tell you the moment you overwrite the last pointer to
non-freed
> > memory (though I think you'll need to link to glibc).
>
> FYI, I've built valgrind vs uClibc and it works just fine...
>
>  -Erik
>
> --
> Erik B. Andersen             http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
>