Bugs in a debugging tool? (KMM memory leak detector.)

From: Raptor (bogus_at_none.com)
Date: 02/20/05 

Date: Sat, 19 Feb 2005 21:48:54 -0800

Finally getting around to installing the memory leak detector a couple of
folks have recommended.
(http://bdn.borland.com/article/0,1410,28344,00.html)

Well, the documentation is pretty good, but...

After the usual hassles, I was able to get the thing to compile OK.

Bad sign #1: The precompiled demo project wouldn't run right--it gives the
same error on every button-push as #2 below. REEEAL bad sign.

Bad sign #2: A fresh project, just a form, the lucid How-To instructions
followed to the letter, the "app" form comes up OK, but at shut-down it goes
Bing! and gives me "Runtime error 201 at 00003BF0."

Commenting out the {$I DebugDef.inc} makes the problem go away. No output
files are generated, as is apparently supposed to happen. I narrowed the
problem down to the single line in the MemReport procedure which calls the
kmGetAutopsy, which I think is in the DLL.

I have the DLL code as well, but I'm not sure how to debug the DLL code
while running a sample project which calls it--time to beef up my limited
debugging skills.

Suggestions?

Raptor

Quantcast