From owner-freebsd-hackers Sat Oct 31 06:24:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00415 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 06:24:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00408 for ; Sat, 31 Oct 1998 06:24:49 -0800 (PST) (envelope-from rjs@fdy2.demon.co.uk) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.8/8.8.8) id OAA00539; Sat, 31 Oct 1998 14:20:45 GMT (envelope-from rjs) Date: Sat, 31 Oct 1998 14:20:45 GMT Message-Id: <199810311420.OAA00539@fdy2.demon.co.uk> From: Robert Swindells To: joelh@gnu.org CC: kline@thought.org, hackers@FreeBSD.ORG In-reply-to: <86u30lms4a.fsf@detlev.UUCP> (message from Joel Ray Holveck on 30 Oct 1998 19:34:29 -0600) Subject: Re: Memory leak location tool? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 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. > >* Doug Lea's malloc (libdlmalloc) and libmalloc include hooks to add > leak detection. > >* S-Lang (libslang) says that it includes "a malloc debugging > package". I'm not sure whether they mean something to help debug > malloc, or a malloc that helps you debug your code. There is also a simple one as part of X11R6.3. It is in xc/utils/memleak. I can't tell if the 386 support came as standard, or with the XFree86 patches. Robert Swindells ------------------------------------- Robert Swindells - GenRad Ltd rjs@genrad.co.uk - Work rjs@fdy2.demon.co.uk - Home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message