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.

1, Modify you project's code.
Place the unit "Denomo.pas" as the very first unit under the "uses" section in your project's .dpr file.
If you use another memory manager explicitly, e.g, FastMM, put the unit "Denomo.pas" just under the memory manager.
2, Change project options in Delphi project.
In Delphi, in your project to detect memory leak, go to menu Project->Options->Compiler, be sure "Optimization" is unchecked, and "Stack frames", "Debug information", "Reference info", "Definitions only", "Assertions", and "Use Debug DCUs" are checked.
3, Compile and run your project.
4, Run binLeakInspector 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.

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.
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, Eliminate leaked child objects created in constructor.
If any objects created in object A's constructor, then if A is leaked (not freed), the objects created in its constructor will not be reported as leak.
This feature will significantly suppress the leak report amount so to make you focus on the objects that are really leaked..
5, Leak detection during a certain session.
You can inspect the memory leak during a certain period rather than only monitor the whole program life.
6, Leak source locations.
Denomo can report exact source information such as unit name, procedure name, line number, if JCL is used and TD32 debug information is available.
7, Leak report on program exit.
Just like many other memory leak detection tools do.
8, Free Twice detection.
If the program free a memory block that has been freed, Denomo can detect and report it.
9, Don't depend on any memory manager.
If the default memory manager is not compatible with leak detection, Denomo also has a simple Windows heap based memory manager with it.
10, Works on Delphi 6, Delphi 7 and Delphi 2007.
Other versions Delphi are not tested on. You will be much appreciated if you test this work with Delphi 5, Delphi 2005, 2006, and any other 32 bits Delphi versions.