From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id EA04A8018D for ; Fri, 30 Jun 2017 01:16:37 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.40,283,1496095200"; d="scan'208";a="230050474" Received: from unknown (HELO hadrien.local) ([50.233.144.2]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jun 2017 01:16:36 +0200 Date: Thu, 29 Jun 2017 17:16:34 -0600 (MDT) From: Julia Lawall X-X-Sender: jll@hadrien To: Damien Doligez cc: Julia Lawall , SP , caml users In-Reply-To: <8615B281-0D8A-45F0-937F-C70F4F18ABDC@inria.fr> Message-ID: References: <88108a18-8044-bc46-bed3-aef241b4ff48@linux-france.org> <8615B281-0D8A-45F0-937F-C70F4F18ABDC@inria.fr> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Subject: Re: [Caml-list] segmentation fault 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? The person who reported the bug does have one of the offending machines and had hyperthreading enabled. He is going to try with hyperthreading disabled. $ cat /proc/cpuinfo | grep "model" model : 78 model name : Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz model : 78 model name : Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz model : 78 model name : Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz model : 78 model name : Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz $ grep -q '^flags.*[[:space:]]ht[[:space:]]' /proc/cpuinfo && echo "Hyper-threading is supported" Hyper-threading is supported julia > > Cheers, > > -- Damien > > > On 2017-06-23, at 19:25, Julia Lawall 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 > >