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 nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id 97602BB9A for ; Tue, 15 Nov 2005 06:32:21 +0100 (CET) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id jAF5WK38019367 for ; Tue, 15 Nov 2005 06:32:21 +0100 Received: by zproxy.gmail.com with SMTP id x3so1542971nzd for ; Mon, 14 Nov 2005 21:32:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KNNwdQQQmtTZYSUjCTOwZPyhksscUwd/gB9esz8ujmEJcVof2CqRI68b+UZHfkrX0kw19snvwJmVlv211IGlOFEUZrP9WlrDfTuBQe1NZf35OcB4N9fou/Zejyvdq1uXwaBQeX0D7MgN5L0S9zOdIseBhhyOlhHc41LJswua5g8= Received: by 10.65.20.6 with SMTP id x6mr4404736qbi; Mon, 14 Nov 2005 21:32:20 -0800 (PST) Received: by 10.64.10.5 with HTTP; Mon, 14 Nov 2005 21:32:19 -0800 (PST) Message-ID: Date: Tue, 15 Nov 2005 18:32:20 +1300 From: Jonathan Roewen Subject: Re: [Caml-list] ocamlc -output-obj problems Cc: caml-list@yquem.inria.fr In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1132028623.11813.99.camel@rosella> X-Miltered: at nez-perce with ID 437972E4.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 ocamlc:01 -output-obj:01 ocaml:01 segfaults:01 makefile:01 loader:01 printf:01 ...:98 ...:98 wrote:01 caml:02 hmm:02 declaration:02 commenting:03 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_BY_IP autolearn=disabled version=3.0.3 On 11/15/05, Jonathan Roewen wrote: > Hmm, I made a test case to run with system ocaml tools. It segfaults > =3D/ So, perhaps this is what's happening in my OS -- except I don't > have anything to catch something like that... > > I've attached it. Very, very simple. Makefile, bytekernel.ml that has > same problems on my OS, and c_loader.c that calls caml_startup() same > way as I do in my OS. > > So perhaps it isn't just my imagination ;-) > > Hell if I know what's wrong either... > > Jonathan > > > I should also note: commenting out the printf declaration, it runs fine.