Subj : Re: Finding a resource leak using Memproof and Codeguard
To   : borland.public.cpp.borlandcpp
From : "Sebastian Ledesma" <labo(no_sp@m)solidyne1.com>
Date : Wed Mar 03 2004 11:25 am

Hi Richard:

I also use Memproof and Codeguard too. Memproof reports more memory leaks
that Codeguard but I only found
one reason to explain it (does not explain everything): the GDI system
(assuming you are using OWL) uses a cache
to avoid requesting/freeing GDI objects every time.
Hope this helps.

Saludos
Sebastian

"Richard Hufford" <support@thesystem.com> escribió en el mensaje
news:404507c3$1@newsgroups.borland.com...
> I've been looking for bugs in my 32-bit C++ program developed with Borland
> C++ 5.01.  When I run the program using Memproof, I have a situation in
> which the "Pointers" line on the Memproof main window counts thousands of
> pointers whenever a window is repainted, and the counts never go back
down.
> If I run the program with Codeguard, instead of Memproof, I get about 15
> resource leaks reported when the program terminates; these resource leaks
> are variables that are created when the program starts and have nothing to
> do with repainting the screen.
>   Does this indicate that I have a huge resource leak that Memproof finds,
> but Codeguard does not, or could there be something else going on?
Perhaps
> I just don't understand what Memproof lists as "Pointers".
>
>

.