From: "Richard W.M. Jones" <rich@annexia.org>
To: Damien Doligez <damien.doligez@inria.fr>
Cc: "caml users" <caml-list@inria.fr>,
"Laïka Moussa" <laika.moussa@itelios.com>
Subject: Re: [Caml-list] OCaml release 4.00.0
Date: Sat, 28 Jul 2012 12:23:03 +0100 [thread overview]
Message-ID: <20120728112303.GA5247@annexia.org> (raw)
In-Reply-To: <2F8B839C-9964-4600-9F92-05F9A3A4D7EB@inria.fr>
OCaml 4.00.0 is now in Fedora 18.
We were chasing a very odd and very rare OCaml heap corruption bug in
32 bit i686 binaries build by OCaml 4.00.0 beta 2 which caused
segfaults in programs like ocamlopt.opt and coq:
https://bugzilla.redhat.com/show_bug.cgi?id=843731
I haven't yet tested OCaml 4.00.0 non-beta, but will be doing so next
week. It might be fixed.
Do the symptoms ring any bells?
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2012-07-28 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 12:16 Damien Doligez
2012-07-26 12:58 ` Oliver Bandel
2012-07-28 11:23 ` Richard W.M. Jones [this message]
2012-07-28 15:42 ` Richard W.M. Jones
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=20120728112303.GA5247@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=damien.doligez@inria.fr \
--cc=laika.moussa@itelios.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;
as well as URLs for NNTP newsgroup(s).