caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Christophe Raffalli <Christophe.Raffalli@univ-savoie.fr>
To: Christophe Raffalli <Christophe.Raffalli@univ-savoie.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] FreeBSD + lablglut + thread: bug or not bug
Date: Thu, 11 Sep 2003 16:25:24 +0200	[thread overview]
Message-ID: <3F6085D4.1020106@univ-savoie.fr> (raw)
In-Reply-To: <3F607D6F.4010405@univ-savoie.fr>

Christophe Raffalli wrote:
> Her is a small file (simplified from GlSurf)
> that SEGV on FreeBSD 4.3 (with NVidia driver ...) and ocaml-3.07beta2

FreeBSD 4.8 not 4.3 !!

> If you remove the line with thread.yeld it does not SEGV. note:
> thread.yeld is not called since Glut.mainLoop is not started, so I am
>  puzzled.
> 
> Note: all the examples in lablglut distributions appear to work on my 
> FreeBSD box and the same program (GlSurf) works on Linux, windows and OSX.
> 
> So there is a problem when you use FreeBSD+lablGL/GLUT+thread (you need 
> the three of them)
> 
> Here is the file:
> 
> -- test.ml
> 
>     ignore(Glut.init Sys.argv);
>     Glut.initDisplayMode ~alpha:true ~double_buffer:true ~depth:true () ;
>     Glut.initWindowSize ~w:300 ~h:300;
>     ignore (Glut.createWindow ~title:"bug demo");
>     Glut.idleFunc (Some Thread.yield);
>     print_string "titi";
>     print_newline ()
> 
> -- 
> 
> And the line used to compile it
> 
> ocamlc -o testbug functionstubs.o -thread -labels -I +lablglut -I 
> +lablGL -I +threads -pp "camlp4o pa_ifdef.cmo -DUNIX" -thread unix.cma 
> threads.cma lablglut.cma lablgl.cma -cclib -lGL -cclib -lGLU -cclib 
> -lXmu test.ml
> bash-2.05b$ ./testbug
> Segmentation fault (core dumped)
> 

-- 
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex

tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature
---------------------------------------------

-------------------
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-09-11 14:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 18:52 [Caml-list] suggestion for record pattern matching and construction Eric C. Cooper
2003-09-10 23:19 ` Olivier Andrieu
2003-09-14 19:32   ` brogoff
2003-09-11 13:49 ` [Caml-list] FreeBSD + lablglut + thread: bug or not bug Christophe Raffalli
2003-09-11 14:25   ` Christophe Raffalli [this message]
2003-09-11 14:30   ` Gerd Stolpmann
2003-09-11 15:11     ` Christophe Raffalli
2003-09-11 15:23       ` Gerd Stolpmann
2003-09-11 17:33   ` Issac Trotts
2003-09-11 20:01     ` Christophe Raffalli
2003-09-11 20:09     ` Christophe Raffalli
2003-09-11 20:38       ` Issac Trotts
2003-09-12  5:57       ` Christophe Raffalli
2003-09-12  6:34         ` Gerd Stolpmann
2003-09-22 12:16         ` Christophe Raffalli

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=3F6085D4.1020106@univ-savoie.fr \
    --to=christophe.raffalli@univ-savoie.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;
as well as URLs for NNTP newsgroup(s).