From: Markus Mottl <markus@oefai.at>
To: Berke Durak <berke@altern.org>
Cc: caml-list@inria.fr, caml-bugs <caml-bugs@pauillac.inria.fr>
Subject: Re: [Caml-list] Native threads under Debian 3.0r0
Date: Wed, 4 Sep 2002 11:44:32 +0200 [thread overview]
Message-ID: <20020904094432.GA1375@kiefer.ai.univie.ac.at> (raw)
In-Reply-To: <20020903230314.GA311@gogol>
On Wed, 04 Sep 2002, Berke Durak wrote:
> I'm having severe problems with native threads. Not only I can't get them to
> work with the Graphics module, I can't get them to work at all. I'm
> using a fresh Debian 3.0r0. I've recompiled Ocaml 3.06 with
> '-with-pthread' option. Shouldn't the following code
(cross-posted to caml-bugs)
There indeed seems to be something broken about threads (at least native
ones). Things work fine with byte-code and the toplevel, but native
code + native threads don't. I have managed to reproduced this problem
under Linux and Solaris with OCaml 3.06, but also with an older version
(3.04+10 - 2002-04-18) on an Alpha (Digital Unix).
Regards,
Markus Mottl
> $ cat toto.ml
> open Thread
>
> let _ =
> let code1 () =
> let x = ref 0 in
> while true do
> incr x;
> Printf.printf "alpha %d\n" !x;
> flush stdout
> done
> in
> let thread1 = Thread.create code1 ()
> in
> while true do
> ()
> done
>
> compiled with
>
> $ ocamlopt.opt -thread unix.cmxa threads.cmxa toto.ml -o toto
>
> and run as
>
> $ ./toto
>
> give me something like
>
> alpha 0
> alpha 1
> alpha 2
> alpha 3
> alpha 4
> alpha 5
> alpha 6
> ...
>
> ?
>
> Instead, the program doesn't output anything, and when I hit Ctrl-C,
> it leaves some processes running, which can only be killed with
> SIGKILL.
>
> The program works when compiled as bytecode. System info :
>
> $ uname -a
> Linux gogol 2.4.18 #1 Thu Aug 22 20:42:28 CEST 2002 i586 unknown
> $ ls -l /lib/libpthread*
> -rw-r--r-- 1 root root 102172 Apr 28 11:57 /lib/libpthread-0.9.so
>
> However, even in bytecode, when I use the Graphics module, some subprocesses
> refuse to die when I interrupt the main program.
>
> Any clues ? Thanks very much.
> --
> Berke Durak
> -------------------
> 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
--
Markus Mottl markus@oefai.at
Austrian Research Institute
for Artificial Intelligence http://www.oefai.at/~markus
-------------------
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:[~2002-09-04 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 23:03 Berke Durak
2002-09-04 9:44 ` Markus Mottl [this message]
2002-09-04 10:15 ` Jacques Garrigue
2002-09-04 10:39 ` Olivier Andrieu
2002-09-04 13:01 ` Markus Mottl
2002-09-04 15:14 ` Berke Durak
2002-09-04 23:38 ` Jacques Garrigue
2002-09-04 14:38 ` Sven LUTHER
2002-09-05 9:17 ` Stefano Zacchiroli
2002-09-05 10:42 ` Sven LUTHER
2002-09-05 11:37 ` Stefano Zacchiroli
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=20020904094432.GA1375@kiefer.ai.univie.ac.at \
--to=markus@oefai.at \
--cc=berke@altern.org \
--cc=caml-bugs@pauillac.inria.fr \
--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