From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Crashing X.Org with lablgl
Date: Mon, 26 Feb 2007 07:29:28 +0000 [thread overview]
Message-ID: <200702260729.29257.jon@ffconsultancy.com> (raw)
In-Reply-To: <65D985D2-E7EF-42F7-B356-5F8EC2170F17@epfl.ch>
On Monday 26 February 2007 05:51, Daniel Bünzli wrote:
> There are things that are off-limits to lablgl's type safety, for
> example on osx a call to any opengl function before a rendering
> context has been created just crashes the program. Did you try to
> call Gl.raise_error in your rendering loop to be sure you are not
> doing something wrong with opengl ?
The order of initialisation calls can cause segfaults on some machines.
I did some fairly extensive testing before we released Presenta. Around 10% of
machines crashed OpenGL binaries that were moved onto them.
If you want portable (between machines) 3D then try F#, .NET and managed
DirectX.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
OCaml for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2007-02-26 8:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 5:01 David Thomas
2007-02-26 5:26 ` [Caml-list] " Erik de Castro Lopo
2007-02-26 5:38 ` Jacques Garrigue
2007-02-26 5:51 ` Daniel Bünzli
2007-02-26 7:29 ` Jon Harrop [this message]
2007-02-26 16:36 ` David Thomas
2007-02-26 8:01 ` Vu Ngoc San
2007-02-26 10:47 ` Jon Harrop
2007-02-26 11:23 ` Vincent Hanquez
2007-02-26 14:11 ` Jon Harrop
2007-02-26 13:41 ` Vu Ngoc San
2007-02-26 16:16 ` Conrad Hughes
2007-02-26 19:23 ` Vu Ngoc San
2007-02-26 7:07 David Thomas
[not found] <20070226.161259.96686096.garrigue@math.nagoya-u.ac.jp>
2007-02-26 7:39 ` David Thomas
2007-02-26 11:09 ` Gerd Stolpmann
2007-02-26 16:46 ` David Thomas
2007-02-26 11:21 ` Erik de Castro Lopo
2007-02-26 17:05 ` David Thomas
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=200702260729.29257.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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