caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Christophe Raffalli <Christophe.Raffalli@univ-savoie.fr>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] FreeBSD + lablglut + thread: bug or not bug
Date: Thu, 11 Sep 2003 17:11:51 +0200	[thread overview]
Message-ID: <3F6090B7.2090801@univ-savoie.fr> (raw)
In-Reply-To: <1063290613.18964.3.camel@ares>

Complement:

GlSurf 2.0 that uses no thread works on my BSD Box (so it is not a 
problem with the NVidia driver for FreeBSD)

GlSurf 2.1 also crashes with vmthread ... but a bit later and this is 
more difficult to reproduce . (I can send the source if you want, but it 
is not ready for distribution)

I know that NVidia driver are not thread safe, but only yhe main thread 
does openGL call and it works for Linux.

Gerd Stolpmann wrote:
> Am Don, 2003-09-11 um 15.49 schrieb Christophe Raffalli:
> 
>>Her is a small file (simplified from GlSurf)
>>that SEGV on FreeBSD 4.3 (with NVidia driver ...) and ocaml-3.07beta2
>>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)
> 
> 
> Maybe another incarnation of this (non-)bug:
> 
> http://caml.inria.fr/bin/caml-bugs/not%20a%20bug?id=1820;page=47;user=guest
> 
> It seems that FreeBSD's libc_r is not stable enough.
> 
> Gerd

-- 
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 15:10 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
2003-09-11 14:30   ` Gerd Stolpmann
2003-09-11 15:11     ` Christophe Raffalli [this message]
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=3F6090B7.2090801@univ-savoie.fr \
    --to=christophe.raffalli@univ-savoie.fr \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    /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).