From: "Dmitry Bely" <dmitry.bely@gmail.com>
To: "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocaml DLL and memory leaks
Date: Fri, 11 May 2007 17:19:24 +0400 [thread overview]
Message-ID: <90823c940705110619g55524937p669087eaa5408df4@mail.gmail.com> (raw)
In-Reply-To: <464354B2.30806@inria.fr>
On 5/10/07, Xavier Leroy <Xavier.Leroy@inria.fr> wrote:
> > I have an Ocaml module packed into DLL that is dynamically loaded by
> > the main C program. What should I do to free all memory taken by Ocaml
> > runtime when the DLL is unloaded?
>
> This is not possible currently. I agree the OCaml runtime system
> should one day provide a cleanup function to do this.
It turned out that at least for Microsoft C runtime things are not
that bad. If you statically link CRT, it will clean up all resources
itself.
- Dmitry Bely
prev parent reply other threads:[~2007-05-11 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 10:45 Dmitry Bely
2007-05-10 17:21 ` [Caml-list] " Xavier Leroy
2007-05-11 13:19 ` Dmitry Bely [this message]
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=90823c940705110619g55524937p669087eaa5408df4@mail.gmail.com \
--to=dmitry.bely@gmail.com \
--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).