From owner-freebsd-ports@FreeBSD.ORG Sat May 22 12:47:05 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F00D16A52C; Sat, 22 May 2004 12:47:04 -0700 (PDT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7309F43D3F; Sat, 22 May 2004 12:47:03 -0700 (PDT) (envelope-from barner@in.tum.de) Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id B6BDB4885; Sat, 22 May 2004 21:46:32 +0200 (CEST) Date: Sat, 22 May 2004 21:46:32 +0200 From: Simon Barner To: Cole Message-ID: <20040522194632.GB30506@zi025.glhnet.mhn.de> Mail-Followup-To: ports@freebsd.org References: <000701c4402b$a54e73d0$4206000a@stalker> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uQr8t48UFsdbeI+V" Content-Disposition: inline In-Reply-To: <000701c4402b$a54e73d0$4206000a@stalker> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: ports@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Looking for a ports committer for valgrind (Re: Memory Leak) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 May 2004 19:47:05 -0000 --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--