Date: Sun, 23 May 2004 02:25:21 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: doconnor@gsoft.com.au Cc: freebsd-hackers@freebsd.org Subject: Re: Memory Leak Message-ID: <20040523.022521.70796984.imp@bsdimp.com> In-Reply-To: <200405231445.07562.doconnor@gsoft.com.au> References: <000701c4402b$a54e73d0$4206000a@stalker> <200405231445.07562.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200405231445.07562.doconnor@gsoft.com.au>
"Daniel O'Connor" <doconnor@gsoft.com.au> writes:
: -----BEGIN PGP SIGNED MESSAGE-----
: Hash: SHA1
:
: On Sun, 23 May 2004 04:06, Cole wrote:
: > I just wanted to know what programs any of you have used to track down a
: > memory leak in your programs?
: > Also wondering if there is maybe a good tutorial on the subject under
: > FreeBSD or even linux if possible.
: >
: > Im running FreeBSD 4.9 so just looking for something try to help me track
: > it down.
: >
: > Unless there is someone willing to help me with this since ive never really
: > had to do anything like this, else i can easily read something, just kinda
: > need to know a good memory tracing program or something of the sorts.
:
: There is valgrind..
: http://www.rabson.org/#valgrind
:
: I thought it was in ports but I can't see it.
Has anybody gotten valgrind to work with non-trivial threaded
programs? We've had some issues with that...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040523.022521.70796984.imp>