Memory use problem

Martin Liddle martin at tcs02.demon.co.uk
Sun May 6 15:56:54 CEST 2001


In article <1B07E47F.20010506131757.FOO-5823.frank at g-n-u.de>, Frank
Heckenbach <frank at g-n-u.de> writes
>I'm now adding somewhat improved support to trace memory leaks (will
>be uploaded soon).
>
>Simply using the unit HeapMon should show some report about
>non-released pointers at the end of the program. The unit also
>provides a function to generate such a report at an arbitrary point
>during a program run and to an arbitrary file.
>
>The report contains the caller address (which can be turned to
>source lines using addr2line) which might help find the leaks.
>
>I suppose this is not currently am important thing to you, but when
>it will become a problem again (to you or anyone else), this should
>now help debugging.
>
We haven't yet located the problem so this will be very useful.  Thank
you very much.
-- 
Martin Liddle, Tynemouth Computer Services, 27 Garforth Close, 
Cramlington, Northumberland, England, NE23 6EW.
Phone: 01670-712624.  Fax: 01670-717324.
Web site: <http://www.tynecomp.co.uk>.




More information about the Gpc mailing list