From: Vincenzo Ciancia <vincenzo_yahoo_addressguard-gmane@yahoo.it>
To: caml-list@inria.fr
Subject: Re: Memory leak with ocaml 3.09 but not with ocaml <= 3.08.1
Date: Fri, 25 Nov 2005 10:19:47 +0100 [thread overview]
Message-ID: <dm6kt6$9rt$1@sea.gmane.org> (raw)
In-Reply-To: <87hda26s55.fsf@mid.deneb.enyo.de>
Florian Weimer wrote:
>> leave_blocking_section();
>
>> vpath = copy_string(path);
>
> I don't think it's allowed to invoke the Caml allocator while not
> holding the run-time library lock.
That's why I hold the lock by calling "leave_blocking_section" at the
beginning of the function - it's "enter_blocking_section" that releases the
lock :)
I guess I will have to exclude pieces of code until the memory leak
disappears...
V.
--
Please note that I do not read the e-mail address used in the from field but
I read vincenzo_ml at yahoo dot it
Attenzione: non leggo l'indirizzo di posta usato nel campo from, ma leggo
vincenzo_ml at yahoo dot it
prev parent reply other threads:[~2005-11-25 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 0:00 Vincenzo Ciancia
2005-11-24 14:24 ` [Caml-list] " Florian Weimer
2005-11-25 9:19 ` Vincenzo Ciancia [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='dm6kt6$9rt$1@sea.gmane.org' \
--to=vincenzo_yahoo_addressguard-gmane@yahoo.it \
--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).