Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jean-Marc EBER <jeanmarc.eber@lexifi.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Floating exception
Date: Tue, 27 Nov 2007 14:53:08 +0100	[thread overview]
Message-ID: <474C2144.6010601@lexifi.com> (raw)
In-Reply-To: <200711271119.26078.jon@ffconsultancy.com>

I understand from your mail that the problem source is probably linked to the 
graphics part (either the OCaml binding or the OpenGL implementation itself) and 
not to OCaml's code generation or "binary production" feature. This confirms my 
intuition.

Jean-Marc



Jon Harrop a écrit :
> On Tuesday 27 November 2007 10:24, you wrote:
>> Jon Harrop a écrit :
>>> Too many of our users found the binary generated by ocamlopt to be
>>> unusably unreliable, typically due to random segfaulting that we could
>>> not reproduce.
>> Could you please elaborate ?
> 
> There isn't really anything more that I can add. We wrote the OCaml the 
> obvious way (no unsafe code) and used the conventional bindings (LablGL) and 
> distributed the binary, only to find that too many people had reliability 
> problems for it to be a viable product so we pulled it.
> 
> Now we're trying to give it away in bytecode form and even that is a major 
> PITA because we need to install and compile against (including dependencies) 
> several different minor-minor versions of OCaml just to garner enough 
> interest to find out (from the only person who has given us feedback having 
> managed to compile it out of 75 downloads so far this month) that even these 
> trivial demos don't work.
> 
> My guess is that the glut libraries installed on these computers are causing 
> the problems. Perhaps we should write bindings to GLX or use LablGTK2 to 
> evade glut and see what happens but, of course, we cannot reproduce the 
> problem here and there are a huge number of variations we could try without 
> having any real idea of what is going wrong.
> 


  reply	other threads:[~2007-11-27 13:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23 18:08 Sebastien Ferre
2007-11-23 22:36 ` [Caml-list] " Jon Harrop
2007-11-24  8:23   ` Vu Ngoc San
     [not found]     ` <200711242236.24433.jon@ffconsultancy.com>
2007-11-25  8:26       ` Vu Ngoc San
2007-11-25 15:35         ` [Caml-list] Smoke on 3.09.2 Jon Harrop
2007-11-25 18:26           ` Jon Harrop
2007-11-25 20:12             ` Vu Ngoc San
2007-11-25 20:48               ` Jon Harrop
2007-11-25 21:20                 ` Vu Ngoc San
2007-11-25 21:22                   ` Jon Harrop
2007-11-27 10:24   ` [Caml-list] Floating exception Jean-Marc EBER
2007-11-27 11:19     ` Jon Harrop
2007-11-27 13:53       ` Jean-Marc EBER [this message]
2007-11-27 15:35       ` Richard Jones
2007-11-27 18:13         ` Jon Harrop
2007-11-28 10:47       ` Vu Ngoc San
2007-11-28 14:48         ` Jon Harrop
2007-11-29 14:39         ` Vu Ngoc San
     [not found] ` <1195900308.7242.19.camel@localhost>
2007-11-26 17:25   ` Sebastien Ferre
2007-11-26 17:56     ` Dmitry Bely
2007-11-27  0:01     ` Richard Jones
2007-11-27  6:56       ` Sebastien Ferre

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=474C2144.6010601@lexifi.com \
    --to=jeanmarc.eber@lexifi.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=jon@ffconsultancy.com \
    /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