# heaptrc

heaptrc is a unit that can be used to debug allocation and deallocation of memory blocks. It keeps track of calls to getmem/freemem, and, implicitly, of New/Dispose statements.

Warning: Do not add the heaptrc unit manually. The heaptrc unit needs to be loaded before lineinfo and only the compiler can do that.
Heaptrc is also a memory manager, so don't try to use any memory manager - including heaptrc itself - in the uses clause, because that may lead to memory corruption and false results.
This topic contains a note with example code to handle such a case in a generic way.

When a program using heaptrc ends, heaptrc can write out the total memory used and a list of allocated but not freed blocks to a file. When run in the console (*nix or Windows), heaptrc will print this output to screen unless otherwise instructed. In Lazarus GUI programs on Windows, the output will appear in numerous small dialog boxes, which may be very unpractical, although you can redirect output to file.

On *nix (including BSD, Linux and Mac OS X), by default, nothing will be shown for GUI programs. See leakview for details on how to make use of heaptrc effectively.

## Usage

### Using heaptrc in FPC

Add a parameter -gh to your compilation command line or to fpc.cfg

fpc -gh helloworld.pas


or usually combined with line info:

fpc -glh helloword.pas


This will add heaptrc implicitly as a hidden first unit of the program's uses clause.

You can test in code if heaptrc is active by examining the global variable UseHeapTrace for the presence of heaptrc and its status like so:

program testforheaptrace;
begin
{$if declared(UseHeapTrace)} writeln('Heaptrc is used.',' Heaptrc is active? ', UseHeaptrace) // heaptrc reports can be turned off when linked in... so true or false // you can subsequently test or set any of the heaptrc reporting options here. {$else}
writeln('No trace of heaptrc');
{$ifend} end. ### Using heaptrc in Lazarus To enable this in your Lazarus project: go to Project Options/Linking and in the Debugging section enable Use Heaptrc unit (check for mem-leaks) (-gh) You can test for the presence of heaptrc in a similar manner as in the above example by testing for the presence of UseHeapTrace in your project.lpr file. {$if declared(UseHeapTrace)}
//... do something
// test if active
if UseHeapTrace then ....// Test if reporting is on
{$ifend} ### Show report only on leak If you want to show heaptrc report dialog only if there were leaks in your application, then put this command somewhere in your main project source file:  {$if declared(UseHeapTrace)}
GlobalSkipIfNoLeaks := true; // supported as of debugger version 3.2.0
{$ifend} ### Programmatically disable report If you want to disable report from your code then you can directly manipulate UseHeapTrace variable at program startup  UseHeapTrace := false; This will in effect change the behavior to a normal memory manager. ### Continue execution even on heap error If you want your application to continue execution even in case of a heap error then manipulate HaltOnError variable at program startup  HaltOnError := false; ### Redirect report to file If you want to redirect leak report to file then add this to beginning of you main project file:  SetHeapTraceOutput('trace.log'); // supported as of debugger version 3.2.0 ### Why heaptrc should not be added to the uses clause manually You should never add heaptrc manually in a normal program, because the heaptrc unit needs to be loaded before lineinfo for debugging to work properly. Decoding dwarf debugging info efficiently requires a working heap manager and this means that heaptrc needs to be loaded before the the dwarf line info decoding unit which is loaded by -gl, so heaptrc cannot be used explicitly. Only the compiler itself can insert the unit in its proper place as a hidden first unit in the uses clause. Adding the unit by hand can cause all kind of unwanted side effects. E.g. crashes, reported lineinfo is not reliable and not all leaks can reliably be reported. This has always been the case, but is only properly documented from FPC version 3.0.2. So if you still see heaptrc in your uses clause, remove it! for debugging and reporting to work properly. Note: If your program is designed to use an alternative memory manager, you can adapt your program's uses clause like so: program test; {$mode objfpc}
uses
// This will conditionally switch in a memory manager
// based on the presence of heaptrc
{$if not declared(UseHeapTrace)}cmem,{$ifend}sysutils,classes; // the latter two are just to test.
begin
{$if declared(UseHeapTrace)} writeln('Heaptrc is used.',' Heaptrc is active? ', UseHeaptrace); {$else}
writeln('No trace of heaptrc');
{\$ifend}
end.
In the above example the conditional in the uses clause makes sure that the cmem memory manager is only compiled in if the heaptrc option is not used.