From: Lodewijk Voge <lodewijk@reddwarf.xs4all.nl>
To: caml-list@inria.fr
Subject: Re: [Caml-list] memory leak in C snippet?
Date: Fri, 31 Dec 2004 12:14:21 +0100 [thread overview]
Message-ID: <1EA5D7CE-5B1D-11D9-9722-000A95A068A6@reddwarf.xs4all.nl> (raw)
In-Reply-To: <41D51D75.5010406@wanadoo.fr>
On 31-dec-04, at 10:35, Matthieu Brucher wrote:
> I'm not very into Ocaml at the moment, so perhaps what I will say
> isn't relevant, but you seem to allocate 2 memory blocs in your
> function (alloc_string and alloc_tuple), but where do you free this
> memory ? Does OCaml take charge of this or do you still have to do it
> yourself as it is in a C function ?
no, ocaml is supposed to do this. if it didn't, the daemon wouldn't
last an hour, let alone a week :)
I think I'll file this as a bug and see what the gurus have to say
about it. I'm staring myself silly at the code snippet and the manual
and it's not helping.
Lodewijk
next prev parent reply other threads:[~2004-12-31 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 19:32 Lodewijk Voge
2004-12-31 9:35 ` [Caml-list] " Matthieu Brucher
2004-12-31 11:14 ` Lodewijk Voge [this message]
2004-12-31 15:10 ` Jon Harrop
2004-12-31 15:48 ` Lodewijk Voge
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=1EA5D7CE-5B1D-11D9-9722-000A95A068A6@reddwarf.xs4all.nl \
--to=lodewijk@reddwarf.xs4all.nl \
--cc=caml-list@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).