From: Markus Mottl <markus@oefai.at>
To: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] "noalloc" + enter/leave blocking section - safe?
Date: Mon, 2 Aug 2004 17:15:02 +0200 [thread overview]
Message-ID: <20040802151502.GA10950@fichte.ai.univie.ac.at> (raw)
In-Reply-To: <20040802104349.GA6997@fichte.ai.univie.ac.at>
On Mon, 02 Aug 2004, Markus Mottl wrote:
> one important question: is it safe to use "noalloc" with
> C-functions that contain calls to "caml_enter_blocking_section" and
> "caml_leave_blocking_section" to allow other POSIX-treads?
Ok, after having done some experiments on my own now, it seems that this
is _not_ safe. Here is a small example that demonstrates this:
file: foo.ml
---------------------------------------------------------------------------
external foo : 'a -> unit = "foo_stub" "noalloc"
let thread () =
let ar = Array.init 1 (fun _ -> "") in
foo ();
let ar = Array.init 1 (fun _ -> "") in
()
let () =
let n = 10 in
let ar = Array.create n () in
let tids = Array.map (Thread.create thread) ar in
Array.iter Thread.join tids
---------------------------------------------------------------------------
file: foo_stubs.c
---------------------------------------------------------------------------
#include <caml/mlvalues.h>
#include <caml/signals.h>
CAMLprim value foo_stub(value v) {
caml_enter_blocking_section();
int i;
for (i = 0; i < 100000000; i++);
caml_leave_blocking_section();
return Val_unit;
}
---------------------------------------------------------------------------
Compiling and linking the above example to native code (i.e. with
POSIX-threads) and running it will almost immediately produce a segfault
on my machine. Removing "noalloc" solves this problem.
Could the documentation on the C-interface please be updated with a
small section on the correct use of "noalloc"? It's not documented at
all right now! (This also closes bug report #3019, I guess).
Regards,
Markus
--
Markus Mottl http://www.oefai.at/~markus markus@oefai.at
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-08-02 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 10:43 Markus Mottl
2004-08-02 15:15 ` Markus Mottl [this message]
2004-08-02 15:34 ` Jere Sanisalo
2004-08-02 15:49 ` Falk Hueffner
2004-08-02 16:02 ` Richard Jones
2004-08-02 16:32 ` Markus Mottl
2004-08-02 16:39 ` Falk Hueffner
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=20040802151502.GA10950@fichte.ai.univie.ac.at \
--to=markus@oefai.at \
--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