Date: Sat, 22 May 2004 21:46:32 +0200 From: Simon Barner <barner@in.tum.de> To: Cole <cole@opteqint.net> Cc: freebsd-hackers@freebsd.org Subject: Looking for a ports committer for valgrind (Re: Memory Leak) Message-ID: <20040522194632.GB30506@zi025.glhnet.mhn.de> In-Reply-To: <000701c4402b$a54e73d0$4206000a@stalker> References: <000701c4402b$a54e73d0$4206000a@stalker>
next in thread | previous in thread | raw e-mail | index | archive | help
--uQr8t48UFsdbeI+V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > 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[1] of valgrind [2]. 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 [3]? 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, ... Simon [f'up2 ports@ set] [1] http://www.rabson.org/#valgrind [2] http://valgrind.kde.org/ [3] http://home.leo.org/~barner/freebsd/valgrind/ --uQr8t48UFsdbeI+V Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAr64YCkn+/eutqCoRAhhHAKDVLT9xkSZF1ysp7OpVigpOOxE/WACfX8ZG EZ+7Vxs/2yJw8JARf2y1kS4= =sH5/ -----END PGP SIGNATURE----- --uQr8t48UFsdbeI+V--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040522194632.GB30506>