Getting a longer stacktrace from FastMM?

Question

When FastMM logs a memory leak it includes a stacktrace going back 9 calls. Problem is that the stacktrace is too general to locate the problem easily. The last function call in the trace is called at least 50 times and the object leaked is a very common one.

What can I do to make the stacktrace longer?

Tips to locate leaks more easily are of course welcome, the objects leaked are mostly interfaces, so it's something with cross-referencing or _ReleaseRef not called.

I'm on Delphi 7, using the FastMM492.

Answer 1

Change the StackTraceDepth constant in FastMM4.pas.