[m-dev.] track down a memory leak

[Fergus Henderson]

On 12-Sep-2000, Peter Ross <peter.ross at miscrit.be> wrote:
> I have the unfortunate problem that the heap only grows running under
> the grade hlc.par.gc under windows, I have finally got a DLL built with
> GC_generate_random_backtrace() available.  However it prints out
> nothing!
> 
> Any ideas what to do next?

Don't forget that you have to explicitly invoke
GC_generate_random_backtrace(), e.g. from the gdb prompt -- simply
having an executable built that includes the function won't make it
get called.

If you were already calling GC_generate_random_backtrace(), and it
wasn't producing any output, I'd try setting a breakpoint at
GC_printf(), which should get called from
GC_generate_random_backtrace(), and tracing through it to find out
what the output would have been and why the output doesn't go to the
screen.

If you don't get any hits there, set a breakpoint on or in
GC_generate_random_backtrace() and trace through that
to find out why it isn't calling GC_printf().

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------