From owner-freebsd-hackers@FreeBSD.ORG Sun May 23 12:05:48 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2536716A4D4 for ; Sun, 23 May 2004 12:05:48 -0700 (PDT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF11043D1F for ; Sun, 23 May 2004 12:05:47 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i4NJ5QIX012790; Sun, 23 May 2004 15:05:26 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200405231445.07562.doconnor@gsoft.com.au> References: <000701c4402b$a54e73d0$4206000a@stalker> <200405231445.07562.doconnor@gsoft.com.au> Date: Sun, 23 May 2004 15:05:25 -0400 To: "Daniel O'Connor" , freebsd-hackers@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: Memory Leak X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 May 2004 19:05:48 -0000 At 2:45 PM +0930 5/23/04, Daniel O'Connor wrote: > >There is valgrind.. >http://www.rabson.org/#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 To: Cole Cc: ports@freebsd.org Cc: freebsd-hackers@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[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 [1] http://www.rabson.org/#valgrind [2] http://valgrind.kde.org/ [3] http://home.leo.org/~barner/freebsd/valgrind/