Tips before FastMM commissioning

The person who gave the presentation had some excellent tips which 
will save you reading the readme file:

1. In the DPR, make FastMM the first unit in the uses clause.

2. During development, set compiler directive FullDebugMode and then
Build your project.

3. Before you run your project, copy FastMM_FullDebugMode.dll to the
same folder as your EXE (or any place on your Windows path).

4. Under Project > Options > Linker, make sure that a detailed map
file is created.

Run your project and then exit it. If there were memory leaks, you
will receive a report upon exiting your project. Details will be in
a .txt file in the same folder as the EXE file.

FWIW, starting today, we are going through every single component to
test for leaks. I'll leave details in the release notes for anything
found + fixed. Once that is done, we will start testing aserver.exe
as a whole, and then I should be able to give you some useful details
about how to deal with the PAGE command and trapped exceptions.

Guess you like

Origin blog.csdn.net/shaken/article/details/3405726