From: Stefano Zacchiroli <zack@bononia.it>
To: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] bytecode threads which don't start
Date: Mon, 14 Jul 2003 14:34:14 +0200 [thread overview]
Message-ID: <20030714123414.GA2075@fistandantilus.takhisis.org> (raw)
I'm the maintainer of a tiny library that can be used to create simple
standalone http servers. The library support different http servers
architecture, including the classical multi threaded one where a new
thread is created to serve each incoming request.
I'm now facing the problem that it works perfectly with pthreads, both
in bytecode and native code, but it doesn't work with bytecode ocaml
threads.
I've debugged a bit the problem and the result is that thread created
with Thread.create simply don't start. The function return but the
function passed as first argument simply doesn't get executed.
I don't know how to debug further more the problem. Unfortuntaly I'm not
able to reproduce the problem with tiny examples. So I'm wondering if I
had used some "prohibited" features that don't fit well with bytecode
threads (I'm for example using both signals and timeouts).
Any hints?
TIA
--
Stefano Zacchiroli -- Master in Computer Science @ Uni. Bologna, Italy
zack@{cs.unibo.it,debian.org,bononia.it} - http://www.bononia.it/zack/
" I know you believe you understood what you think I said, but I am not
sure you realize that what you heard is not what I meant! " -- G.Romney
-------------------
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
reply other threads:[~2003-07-14 12:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030714123414.GA2075@fistandantilus.takhisis.org \
--to=zack@bononia.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