FastMM4 FullDebugMode quick tip: don’t forget to give your EXE access to the correct FullDebugMode.dll
Posted by jpluimers on 2014/03/06
If you run FastMM4 in FullDebugMode, then here are two tips that new (and sometimes existing users) often overlook:
- If you set the
FullDebugModedirective in the IDE, build your project. - Don’t forget to give your EXE access to FastMM_FullDebugMode.dll (x86), or FastMM_FullDebugMode64.dll (x64) which are stored in the FastMM4 download and in the precompiled directory of the source code.
Either put that DLL in your path, or copy it to your EXE directory. - Make sure your EXE can write in the directory of the EXE.
The first makes sure all units are compiled with FullDebugMode (Delphi does not always do that automagically).
The second makes sure your EXE can access the DLL that writes out your *MemoryManager_EventLog.txt file containing memory leaks and other issues FastMM4 detected.
–jeroen
The Wiert Corner - irregular stream of stuff 
Günther the Beautiful said
Is there a way I can set an absolute path to where the FastMM report should be written to?
jpluimers said
That’s a good one. I’m not sure, but think the chances are slim. The best person to ask is Pierre le Riche himself (: https://www.facebook.com/pierre.leriche.75