From: Florian Weimer <fw@deneb.enyo.de>
To: jtbryant@valdosta.edu
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Threads & Fork
Date: Tue, 22 Nov 2005 16:39:07 +0100 [thread overview]
Message-ID: <87wtj07kv8.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <1132673981.13170.17.camel@starlight> (Jonathan Bryant's message of "Tue, 22 Nov 2005 10:39:41 -0500")
* Jonathan Bryant:
> I'm confused as to why the attached code hangs. My understanding of
> Unix.fork () is that it completely clones the current process, which in
> my understanding, clones the processes's threads as well. Apparently,
> though, that is not the case, because I can't join the thread in both
> the parent and the child.
I can't speak for the OCaml run-time, but POSIX fork only duplicates
the current thread, so the new process is essentially single-threaded.
next prev parent reply other threads:[~2005-11-22 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 15:39 Jonathan Bryant
2005-11-22 15:03 ` [Caml-list] " Oliver Bandel
2005-11-22 15:39 ` Florian Weimer [this message]
2005-11-22 15:50 ` Oliver Bandel
2005-11-22 16:01 ` David Teller
2005-11-22 17:32 ` Alexander S. Usov
2005-11-22 20:56 ` Oliver Bandel
2005-11-23 3:34 ` Matthew Hannigan
2005-11-22 16:01 ` Christophe Raffalli
2005-11-22 20:46 ` Oliver Bandel
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=87wtj07kv8.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=caml-list@yquem.inria.fr \
--cc=jtbryant@valdosta.edu \
/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).