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 11:24:33 +0100 [thread overview]
Message-ID: <474BF061.2070604@lexifi.com> (raw)
In-Reply-To: <200711232236.39691.jon@ffconsultancy.com>
Could you please elaborate ?
Afer many years of industrial use and commercial distribution of OCaml generated
binaries especially in the Win32 world (our clients run our software that
includes non trivial bindings to external C routines on many different versions
of Windows and hardware configurations), we could not notice this buggy behaviour.
Jean-Marc Eber
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.
next prev parent reply other threads:[~2007-11-27 10:23 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 ` Jean-Marc EBER [this message]
2007-11-27 11:19 ` [Caml-list] Floating exception Jon Harrop
2007-11-27 13:53 ` Jean-Marc EBER
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=474BF061.2070604@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