From: Julia Lawall <julia.lawall@lip6.fr>
To: Damien Doligez <damien.doligez@inria.fr>
Cc: SP <sp@orbitalfox.com>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] segmentation fault
Date: Thu, 29 Jun 2017 09:26:11 -0600 (MDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1706290925270.3588@hadrien> (raw)
In-Reply-To: <8615B281-0D8A-45F0-937F-C70F4F18ABDC@inria.fr>
On Thu, 29 Jun 2017, Damien Doligez wrote:
> Hi Julia,
>
> This is a long shot, but let's see if this is the Skylake/Kaby Lake
> processor bug. Could you follow the instructions at the beginning of
> https://lists.debian.org/debian-devel/2017/06/msg00308.html
> and tell us if you have one of the buggy processors?
Thanks. I don't have access to my failing machine at the moment, but I
will forward the message to the person who reported the problem in the
first place.
julia
>
> Cheers,
>
> -- Damien
>
> > On 2017-06-23, at 19:25, Julia Lawall <julia.lawall@lip6.fr> wrote:
> >
> >
> >
> > On Fri, 23 Jun 2017, SP wrote:
> >
> >> You can use `tailcall` attribute to verify if it is tail-call optimised.
> >>
> >> http://caml.inria.fr/pub/docs/manual-ocaml/extn.html#sec246
> >
> > Thanks. For the moment, though, I have no idea what function call is
> > causing the problem.
> >
> > julia
> >
> >>
> >> --
> >> SP
> >>
> >> --
> >> Caml-list mailing list. Subscription management and archives:
> >> https://sympa.inria.fr/sympa/arc/caml-list
> >> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> >> Bug reports: http://caml.inria.fr/bin/caml-bugs
> >>
> >
> > --
> > Caml-list mailing list. Subscription management and archives:
> > https://sympa.inria.fr/sympa/arc/caml-list
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2017-06-29 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 19:41 Julia Lawall
2017-06-19 20:15 ` David MENTRÉ
2017-06-19 20:58 ` Julia Lawall
2017-06-19 21:15 ` Josh Berdine
2017-06-19 21:19 ` Julia Lawall
2017-06-20 1:01 ` Francois BERENGER
2017-06-20 6:34 ` Julia Lawall
2017-06-21 14:20 ` Markus Weißmann
2017-06-23 17:03 ` SP
2017-06-23 17:25 ` Julia Lawall
2017-06-29 15:19 ` Damien Doligez
2017-06-29 15:26 ` Julia Lawall [this message]
2017-06-29 23:16 ` Julia Lawall
2017-06-30 10:55 ` Julia Lawall
2017-06-30 14:06 ` SP
2017-07-01 18:37 ` Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2008-06-03 3:09 Segmentation fault Jacques Le Normand
2008-06-03 14:08 ` [Caml-list] " Berke Durak
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=alpine.DEB.2.20.1706290925270.3588@hadrien \
--to=julia.lawall@lip6.fr \
--cc=caml-list@inria.fr \
--cc=damien.doligez@inria.fr \
--cc=sp@orbitalfox.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