Denomo for C++: an open source comprehensive memory and resource leak detection tool for BCB and VC

Quick start

1, Modify you project's code.

Include the unit "Denomo.h" in your project's source file.

2, To run your project with Denomo, you must put DenomoCPP.dll to the exe directory.

3, Compile and run your project.

4, Run bin\LeakInspector to start monitoring.

5, Click button "Inc Session Leak Begin".

6, Do something you suspect has memory leak.

7, Click button "Inc Session Leak End", then check the output text.

Features and advantages

1, Low level memory leak detection.

Detect memory leak allocated by function GetMem (the kernel function of Delphi memory manager).

2, Object level memory leak detection.

Detect object leak allocated by object constructor. Only for BCB, not for VC.

3, Keep stack trace of the allocate functions.

Once any memory leaked, the stack trace can help you to locate the address where the leak is allocated.

4, Leak detection during a certain session. The most important feature in Denomo.

You can inspect the memory leak during a certain period rather than only monitor the whole program life.

5, Leak source locations.

Denomo can report exact source information such as procedure name, line number, if debug information is available.

6, Leak report on program exit.

Just like many other memory leak detection tools do.
Enabled by default.

7, Huge leak reporting is fast than ever. Handling tens of thousands of leaks is a piece of cake.

The leaking reporting performance has been highly optmized since version 1.0.2.
Testing on a CeleronD 2.0G HZ 512M Ram, reporting around 3000 blocks costs only no more than 10 seconds, 35000 blocks costs about 40 seconds, 70000 blocks costs about 120 seconds.

8, Support GDI leak detection.

And more resource leak detection will be added in the future versions.

9, Works with BCB 5.5, BCB 6, VC 6, and VC 2008 Express Edition.