Re: Memory Leaks and fixing them

[Brian McGroarty <bvmcg yahoo com>]

I've written tools which automatically augment your code to
track memory leaks, pinpointing specifically where in your
source code the memory is being allocated, and whether any
memory is remaining allocated between "begin-checkpoint" and
"end-checkpoint" pairs.

It also ensures that vectorered and non-vectorered new and
delete calls are paired appropriately, looks for variance in the
creation and deletion points of memory within classes and a slew
of other C++isms which could easily be ripped out if C is
desired.

Does a tool like this already exist in open source? If not,
would a party be interested in helping an OSS neophyte put this
in a form appropriate for redistribution?

--- Robert Brady <rwb197@ecs.soton.ac.uk> wrote:
> On Wed, 16 Jun 1999, James Green wrote:
> 
> > Hi all,
> > 
> > With many of the gnome release patches claiming memory leak
> fixes, it
> > seems reasonable to ask if by closing an app (or X entirely
> to close X,
> > Gnome and the WM) you also release any lost memory that
> leaked during
> > execution of that app, or to put it simply:
> > 
> > ...Does closing a app release any memory leaked by that app?
> 
> Yes. This is one of the functions of the operating system : to
> deallocate
> memory allocated to a process when the process dies.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com