Date: Sun, 23 May 2004 15:50:00 -0400 From: Brian Feldman <green@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: hackers@FreeBSD.org Subject: Re: Memory Leak Message-ID: <20040523195000.GB75871@green.homeunix.org> In-Reply-To: <20040522.223042.41645314.imp@bsdimp.com> References: <000701c4402b$a54e73d0$4206000a@stalker> <40AFA163.4020109@freebsd.org> <20040522.223042.41645314.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 22, 2004 at 10:30:42PM -0600, M. Warner Losh wrote: > Any suggestions for leak detectors that work in real-time or in > response to some external signal? In a threaded application would be > ideal. > > I've hacked malloc to add the stack traceback to the utrace info > that's output by malloc. However, for applications that run for days, > and tend to allocate and free a lot of memory, you gotta have lots of > local storage. The restrictions in the kernel that requires this to > be a real file makes it harder. > > Also, there's a difference between what's in use and what is leaking.. Try boehm-gc; I run the following local patch to the ports to fix a few things and let me enable compile options from the ports infrastructure. You can call the detector at any time to see if any leaks have occurred made. <URL:http://green.homeunix.org/~green/boehm-gc.diffs>; -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040523195000.GB75871>