From: Samuel Mimram <samuel.mimram@ens-lyon.org>
To: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] debugging memory leaks
Date: Mon, 12 Nov 2007 23:02:05 +0000 [thread overview]
Message-ID: <4738DB6D.5020001@ens-lyon.org> (raw)
In-Reply-To: <1f4f725e0711121253y2b63cb2ag94af4f0c8642285a@mail.gmail.com>
Hi,
Since I put the patch on my webpage I owe you an apology. If I remember
well, I got the link on IRC while having issues with memory and the only
thing I did was to resolve the conflicts generated by diff. I put it on
the net because it was hard to find and apparently it was useful to
other people. I'm correcting the credits right now.
Regards,
Samuel.
Fabrice Le Fessant wrote:
> Interesting, I did a patch in 2004, called ocaml-memprof for
> ocaml-3.07,but there is not a single reference/credit to it on this
> page... Given the inheritance, the maintainer should be careful to
> keep the original author's name.
>
> - Fabrice Le Fesasnt
> ASAP Project, INRIA Saclay
>
> On Nov 12, 2007 8:53 AM, Pierre Etchemaïté <petchema@concept-micro.com> wrote:
>> Le Sun, 11 Nov 2007 21:56:06 -0800, Chris Waterson <waterson@maubi.net> a écrit :
>>
>>> 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?
>> There's ocaml-memprof, a compiler patch that adds memory profiling
>> features to ocaml programs;
>>
>> Latest update of the patch itself, as far as I know:
>> http://www.pps.jussieu.fr/~smimram/docs/ocaml-3.09.3-memprof.patch
>>
>> Readme:
>> http://www.pps.jussieu.fr/~smimram/docs/README.memprof
>>
>>
>> _______________________________________________
>> Caml-list mailing list. Subscription management:
>> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
>> Archives: http://caml.inria.fr
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2007-11-12 23:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 5:56 Chris Waterson
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 [this message]
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=4738DB6D.5020001@ens-lyon.org \
--to=samuel.mimram@ens-lyon.org \
--cc=Fabrice.Le_fessant@inria.fr \
--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