Getting a longer stacktrace from FastMM?

Asked 23/9, 2009 at 20:43 Answered 24/9, 2009 at 17:1

Solved delphi memory-leaks stack-trace fastmm

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.

Barrettbarrette answered 23/9, 2009 at 20:43 Comment(0)

Change the StackTraceDepth constant in FastMM4.pas.

Smart answered 23/9, 2009 at 20:58 Comment(1)

Ahh, nice one, I will try it tomorrow. I only checked the .inc file. – Barrettbarrette 23/9, 2009 at 21:1

Have a look at FastMM4 Options Interface from Jed Software. It is a freeware application to configre FastMM

Closefisted answered 24/9, 2009 at 17:1 Comment(1)

It looks like that program only adjusts the conditional-compilation options from FastMM4Options.inc. – Smart 24/9, 2009 at 19:19

Recommended topics

Hot tags