From: "Markus Mottl" <markus.mottl@gmail.com>
To: "Andres Varon" <avaron@gmail.com>
Cc: "OCaml List" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] segfault in 3.10.0
Date: Thu, 2 Aug 2007 01:05:43 -0400 [thread overview]
Message-ID: <f8560b80708012205m6e532a86p67462932d053895e@mail.gmail.com> (raw)
In-Reply-To: <7209A0C0-93DC-46A9-940D-47C54EB31E1B@gmail.com>
On 8/1/07, Andres Varon <avaron@gmail.com> wrote:
> Has anyone observed sudden segfaults in OCaml 3.10.0 amd-64 under
> linux?
I would almost bet it's that one:
http://caml.inria.fr/mantis/view.php?id=4300
Avoid enabling native stack backtraces (i.e. don't set
OCAMLRUNPARAM=b=1). I haven't seen any segfaults yet unless these
were turned on in which case you may see them often. Native stack
backtraces unfortunately seem still broken.
Regards,
Markus
--
Markus Mottl http://www.ocaml.info markus.mottl@gmail.com
next prev parent reply other threads:[~2007-08-02 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 21:10 Andres Varon
2007-08-01 22:27 ` [Caml-list] " Andres Varon
2007-08-02 0:39 ` Yaron Minsky
2007-08-02 5:05 ` Markus Mottl [this message]
2007-08-02 15:41 ` Andres Varon
2007-08-02 16:46 ` Alain Frisch
2007-08-02 17:31 ` Andres Varon
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=f8560b80708012205m6e532a86p67462932d053895e@mail.gmail.com \
--to=markus.mottl@gmail.com \
--cc=avaron@gmail.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;
as well as URLs for NNTP newsgroup(s).