From: Chris Waterson <waterson@maubi.net>
To: caml-list@yquem.inria.fr
Subject: debugging memory leaks
Date: Sun, 11 Nov 2007 21:56:06 -0800 [thread overview]
Message-ID: <86183D4E-184A-4F26-84F9-93411D070B38@maubi.net> (raw)
I have a fairly substantial OCaml application that leaks memory.
What tools or techniques do people use to track down memory leaks?
Minimally, is there a way to enumerate the live objects in the heap?
I've tried "valgrind" on a natively-compiled executable, but all the
"real" allocations are hidden in the Caml heap, so it's not very useful.
Any recommendations would be warmly welcomed. Thanks in advance...
chris
next reply other threads:[~2007-11-12 5:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 5:56 Chris Waterson [this message]
2007-11-12 7:53 ` [Caml-list] " Pierre Etchemaïté
2007-11-12 18:07 ` Chris Waterson
2007-11-12 20:53 ` Fabrice Le Fessant
2007-11-12 23:02 ` Samuel Mimram
2010-01-29 4:34 ` warrensomebody
2010-02-02 9:00 ` Richard Jones
2010-02-02 10:28 ` Sylvain Le Gall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86183D4E-184A-4F26-84F9-93411D070B38@maubi.net \
--to=waterson@maubi.net \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).