From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 935C3BC57 for ; Mon, 15 Nov 2010 20:08:35 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArUEAKIT4UxiilpWgmdsb2JhbACUWI4aAQsLCAcTAx+/L4VKBIRaiQk X-IronPort-AV: E=Sophos;i="4.59,201,1288566000"; d="scan'208";a="77948898" Received: from nm23.bullet.mail.ne1.yahoo.com ([98.138.90.86]) by mail4-smtp-sop.national.inria.fr with SMTP; 15 Nov 2010 20:08:34 +0100 Received: from [98.138.90.53] by nm23.bullet.mail.ne1.yahoo.com with NNFMP; 15 Nov 2010 19:08:33 -0000 Received: from [98.138.89.233] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 15 Nov 2010 19:08:33 -0000 Received: from [127.0.0.1] by omp1048.mail.ne1.yahoo.com with NNFMP; 15 Nov 2010 19:08:33 -0000 X-Yahoo-Newman-Id: 678869.71373.bm@omp1048.mail.ne1.yahoo.com Received: (qmail 18711 invoked from network); 15 Nov 2010 19:08:33 -0000 Received: from [192.168.0.2] (norm@76.21.112.227 with plain) by smtp101.sbc.mail.ne1.yahoo.com with SMTP; 15 Nov 2010 11:08:30 -0800 PST X-Yahoo-SMTP: 6wM9MhqswBCJxy9jDcYebttHhXX021oP4RUg3aXahuvJwcSQLA-- X-YMail-OSG: LMIwCcAVM1mlO_heisBXNNna.tMlsCPZUMw0sVp1OkSq4vf kp_fU_mF0egD2yakJ3sQCW5MHi_4dZ30vBEYOXfyeifOmxNmnwxIl3_9uXXR VysgunpDIP65Id5ubgKQyMraTeFDeYq9lZnnBCCmz9jA2HTmTJmjvujz6kFa ilnRyWRvzuVqKsqJg.aJZ3p8RJFSJpusskyMwmxIrNdWwBsyh7QjBhf8adqI BY0M_I4DlrANNV_Jz1zKm__O8yhGbTKMkAYui6UGcpHop8TOwq41473QczP6 eoOnFJVloTxq2rmlerVxhd5qJjZ.Pwu0WQuMy0R2yvlIuL.Pq4MA- X-Yahoo-Newman-Property: ymail-3 References: <384325291.294734.1288998871132.JavaMail.root@zmbs3.inria.fr> <20101106025118.GA23041@yquem.inria.fr> <4CE1792B.3050603@coherentgraphics.co.uk> <157788745.568057.1289846305435.JavaMail.root@zmbs3.inria.fr> <20101115185016.GC12576@yquem.inria.fr> In-Reply-To: <20101115185016.GC12576@yquem.inria.fr> Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii Message-Id: <14603EE6-427C-4004-B07C-1F2B959B9253@cap-lore.com> Content-Transfer-Encoding: quoted-printable From: Norman Hardy Subject: Re: [Caml-list] Causes for segfaults Date: Mon, 15 Nov 2010 11:08:29 -0800 To: caml-list@yquem.inria.fr X-Mailer: Apple Mail (2.1082) X-Spam: no; 0.00; segfaults:01 rauglaudre:01 0100,:01 segfault:01 ocamlopt:01 segfault:01 ocaml:01 runtime:01 uname:01 ocaml:01 -version:01 toplevel:01 ocamlopt:01 usr:01 lib:01 On 2010 Nov 15, at 10:50 , Daniel de Rauglaudre wrote: > On Mon, Nov 15, 2010 at 07:38:25PM +0100, Jamie Brandon wrote: >=20 >> jamie@jamie-aspire:~$ cat > segfault.ml >> let rec ints n =3D n :: ints (n+1) >> let _ =3D ints 0 >> jamie@jamie-aspire:~$ ocamlopt segfault.ml >> jamie@jamie-aspire:~$ ./a.out >> Segmentation fault >=20 > Stack overflow in native code triggers a segmentation fault, indeed. > I think in C, it is the same thing. Not tested in the OCaml runtime > for efficiency purposes, I think. >=20 > -- My 2 cents worth of ideas for efficient and safe stack frame allocation: http://cap-lore.com/code/BigStack.html On Mac: 172% uname -a Darwin apple-s-Computer.local 10.5.0 Darwin Kernel Version 10.5.0: Fri = Nov 5 23:20:39 PDT 2010; root:xnu-1504.9.17~1/RELEASE_I386 i386 172% ocaml -version The Objective Caml toplevel, version 3.12.0 172% cat > segfault.ml let rec ints n =3D n :: ints (n+1) let _ =3D ints 0 172% ocamlopt segfault.ml ld: in /usr/local/lib/ocaml/std_exit.o, indirect symbol index out of = range collect2: ld returned 1 exit status File "caml_startup", line 1, characters 0-1: Error: Error during linking