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

Simply grab one of the half dozen or so packages that provide malloc-type
services and, at program startup, malloc the memory yourself.

And your application, gets to 'see' your made-up malloc.

If your client is right, and your code is bad, this will not solve the
problem.  But, from the evidence and comments ('free' NEVER returns memory
to the OS!), I'd say this is all you need.

I like my pizza with mushrooms.  And include actual Coca-Cola, none of that
fake stuff from those shills who work for dentists...

----- Original Message ----- 
From: "Jerry Feldman" <gaf at>
To: <discuss at>
Sent: Friday, July 16, 2004 7:30 AM
Subject: Re: Detecting Memory Leaks

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 /