Garance A Drosihn
drosih at rpi.edu
Sun May 23 12:05:48 PDT 2004
At 2:45 PM +0930 5/23/04, Daniel O'Connor wrote:
>There is valgrind..
>I thought it was in ports but I can't see it.
Note the separate message:
Date: Sat, 22 May 2004 21:46:32 +0200
From: Simon Barner <barner at in.tum.de>
To: Cole <cole at opteqint.net>
Cc: ports at freebsd.org
Cc: freebsd-hackers at freebsd.org
Subject: Looking for a ports committer for valgrind (Re: Memory Leak)
> I just wanted to know what programs any of you have used to
> track down a memory leak in your programs?
this reminds me of something... :-/
I created a port for Doug Rabson's FreeBSD port of valgrind .
He considered my work ready for the ports tree, but he also said
that that he doesn't do any ports commits these days.
So, could somebody please have a look at the ports (there is a
stable and a development version of valgrind) to be found at ?
If they get committed, PR ports/65585 can be closed as well (also
approved by Doug).
It's a pity that I forgot that excellent memory debugging tool,
most notably because all the work has already been done, and the
ports were only rotting around. :-(
Cole, in order two answer your question at least a little bit:
valgrind is great at detecting memory leaks and much more,
e.g. out-of-bound array access, ...
More information about the freebsd-hackers