From: Dmitry Bely <dmitry.bely@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Using C threads
Date: Fri, 4 Mar 2011 02:03:14 +0300 [thread overview]
Message-ID: <AANLkTikTNreysHtOTrArU=k8t2n-yvj-JcS2DJGL7agk@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikTV8kKKxnhrFp+SMhKi13U8avgK-dV+d9SewzW@mail.gmail.com>
On Fri, Mar 4, 2011 at 1:16 AM, Niki Yoshiuchi <aplusbi@gmail.com> wrote:
> I figured it out so I'm posting it here for reference.
> caml_c_thread_register() attempts to get the master lock, which
> involves dereferencing a pointer. That pointer is initialized by the
> Thread module. However if the OCaml code doesn't use the Thread
> module
Have you specified -thread compiler option? Is it mandatory when using
system threads.
- Dmitry Bely
next prev parent reply other threads:[~2011-03-03 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 21:56 Niki Yoshiuchi
2011-03-01 12:14 ` Dmitry Bely
2011-03-03 22:16 ` Niki Yoshiuchi
2011-03-03 23:03 ` Dmitry Bely [this message]
2011-03-03 23:23 ` Niki Yoshiuchi
2011-03-03 23:38 ` Dmitry Bely
2011-03-03 23:46 ` Niki Yoshiuchi
2011-03-04 0:17 ` Dmitry Bely
2011-03-04 9:21 ` xclerc
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='AANLkTikTNreysHtOTrArU=k8t2n-yvj-JcS2DJGL7agk@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).