This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
To: Balug <balug-talk@balug.org> From: Nick Moffitt <nick@zork.net> Subject: Re: [Balug-talk] Recommendations for a good C Date: Mon, 5 Aug 2002 14:31:51 -0700 begin David L. Sifry quotation: > Can anyone recommend a good memory leak checker for Linux/gcc/gdb? > These are usually implemented as a malloc replacement, but not > necessarily. I see that there are at least 15 or 20 out there, and > I was wondering which oine people use and love, has decent support > for gdb, maybe even does profiling as well, but that's not a > requirment. > > Links appreciated, I will summarize my experiences to the list. [beaujolais(~)] apt-cache search malloc ccmalloc - A memory profiler/debugger dmalloc - Debug memory allocation library (non-threaded) electric-fence - A malloc(3) debugger fda - C malloc debug library gccchecker - Memory access debugger for C language development libgc6 - Conservative garbage collector for C libgc6-dev - Conservative garbage collector for C (development) libleakbug-dev - Development files for GNUpdate leakbug tracer library libleakbug1 - GNUpdate leakbug tracer library manpages-nl - Dutch manpages njamd - Not Just Another Malloc Debugger kmtrace - a KDE memory leak tracer libmm11 - Shared memory library [...libmm duplicates removed...] valgrind - A memory debugger for x86-linux Beware of those Dutch manpages, though! This would probably be a good topic for a Rick Moen Comprehensive List, since it's one tool that many developers either pine for or write from scratch for various reasons. Electric Fence is the most popular, but has its flaws. I know there's a proprietary one that the Samba team use (Jeremy is a big advocate for it), but I forget the name. === To: Nick Moffitt <nick@zork.net> From: "David L. Sifry" <david@sifry.com> Subject: Re: [Balug-talk] Recommendations for a good C Date: 05 Aug 2002 14:52:13 -0700 Thank you Nick, I know of those as well as many others, see http://www.yolinux.com/TUTORIALS/LinuxTutorialSoftwareDevelopment.html as an example of a more comprehensive list. What I'm looking for is actual user experience with these (or other) tools to help me decide what tool is best; a simple triage like that can save a heck of a lot of time. Rational Rose is probably the proprietary one you're thinking of... === To: Marc MERLIN <marc@merlins.org> From: "David L. Sifry" <david@sifry.com> Subject: Re: [Balug-talk] Recommendations for a good C Date: 05 Aug 2002 15:01:12 -0700 On Mon, 2002-08-05 at 14:55, Marc MERLIN wrote: > On Mon, Aug 05, 2002 at 02:52:13PM -0700, David L. Sifry wrote: > > Rational Rose is probably the proprietary one you're thinking of... > > I think it may have been purify You're right, Marc, I stand corrected. === To: "David L. Sifry" <david@sifry.com> From: davidw@dedasys.com (David N. Welton) Subject: Re: [Balug-talk] Recommendations for a good C Date: 05 Aug 2002 15:12:47 -0700 "David L. Sifry" <david@sifry.com> writes: > What I'm looking for is actual user experience with these (or other) > tools to help me decide what tool is best; a simple triage like that > can save a heck of a lot of time. I've heard a lot of good things said about valgrind, although it has the disadvantage of being i386 only, IIRC. One really simple thing to try is the MALLOC_CHECK_ environmental variable as described in malloc(3). > Rational Rose is probably the proprietary one you're thinking of... Purify is the most common one in that space, afaik. ===