From owner-freebsd-hackers Sat Oct 31 18:31:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23012 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 18:31:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23007 for ; Sat, 31 Oct 1998 18:31:46 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id SAA24573; Sat, 31 Oct 1998 18:31:40 -0800 (PST) (envelope-from jdp) Message-Id: <199811010231.SAA24573@austin.polstra.com> To: joelh@gnu.org Subject: Re: Memory leak location tool? In-Reply-To: <86u30lms4a.fsf@detlev.UUCP> References: <19981030141624.A1244@thought.org> <86u30lms4a.fsf@detlev.UUCP> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Sat, 31 Oct 1998 18:31:40 -0800 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <86u30lms4a.fsf@detlev.UUCP>, Joel Ray Holveck wrote: > > Are there any free tools to detect likely memory leaks? Tools > > like Purify aren't quite what I'm looking for. > > Anybody? > > "more `grep -l malloc /usr/ports/devel/*/pkg/DESCR`" will turn up the > following: > > * The Boehm-Weiser garbage collecting malloc (boehm-gc) includes a leak > detector. And I'll just add that it works very nicely indeed. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message