Subj : Finding a resource leak using Memproof and Codeguard
To   : borland.public.cpp.borlandcpp
From : "Richard Hufford" <support@thesystem.com>
Date : Tue Mar 02 2004 03:17 pm

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".

.