Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Detecting Memory Leaks -- the right solution

   From: Jerry Feldman <gaf at>
   Date: Fri, 16 Jul 2004 13:58:06 -0400

   But, even if you do not successfully preempt malloc in the system run
   time libraries, the glibc malloc is still maintaining a separate
   freelist. But, the whole key to this is to look at memory allocations
   occuring in library code. Purify could instrument the libraries on some
   platforms, but I'm not sure that valgrind can. 

Valgrind doesn't seem to have any trouble with this -- it detects
memory leaks in the X libraries, for example.

Robert Krawitz                                     <rlk at>

Tall Clubs International  -- or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lpf at
Project lead for Gimp Print   --

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /