From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.3 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id 975ACBC6C for ; Mon, 26 Nov 2007 18:25:52 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAALKQSkfAXQImh2dsb2JhbACPQAEBAQgKKYEP X-IronPort-AV: E=Sophos;i="4.21,468,1188770400"; d="scan'208";a="4930413" Received: from discorde.inria.fr ([192.93.2.38]) by mail1-smtp-roc.national.inria.fr with ESMTP; 26 Nov 2007 18:25:52 +0100 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id lAQHPpNv005194 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Mon, 26 Nov 2007 18:25:52 +0100 X-IronPort-AV: E=Sophos;i="4.21,468,1188770400"; d="scan'208";a="4930412" Received: from eltanin.irisa.fr (HELO [131.254.14.123]) ([131.254.14.123]) by mail1-relais-roc.national.inria.fr with ESMTP; 26 Nov 2007 18:25:51 +0100 Message-ID: <474B019F.90102@irisa.fr> Date: Mon, 26 Nov 2007 18:25:51 +0100 From: Sebastien Ferre Organization: IRISA User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: ocaml Subject: Re: [Caml-list] Floating exception References: <47471716.3020304@irisa.fr> <1195900308.7242.19.camel@localhost> In-Reply-To: <1195900308.7242.19.camel@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Miltered: at discorde with ID 474B01A0.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; irisa:01 gcc:01 gcc:01 0100,:01 ocaml:01 ocaml:01 3.08:01 distro:01 libs:01 reproduces:01 bug:01 bug:01 14.:98 nguyen:98 ubuntu:98 Hi, I've got the same problem with the simplest program, the "hello world" : let _ = print_string "Hello world!\n" * Machine where compiled (in native code): Linux version 2.6.20-1.2952.fc6 (brewbuilder@ls20-bc1-14.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed May 16 18:59:18 EDT 2007 Intel(R) Core(TM) Duo CPU U2500 @ 1.20GHz * Machine where execution produces "Floating exception" Linux version 2.6.15-1.1833_FC4smp (bhcompile@hs20-bc1-1.build.redhat.com) (gcc version 4.0.2 20051125 (Red Hat 4.0.2-8)) #1 SMP Wed Mar 1 23:56:51 EST 2006 Intel(R) Xeon(TM) CPU 3.40GHz I know I cannot assume that a native binary is portable, but I'd like to understand what makes it fail. gcc version, redhat version, FC version ? Sebastien Kim Nguyen wrote: > On Fri, 2007-11-23 at 19:08 +0100, Sebastien Ferre wrote: >> Hi, >> >> I compiled an OCaml program in native code on >> my new Linux machine. It runs without problem on >> this machine, but crashes as soon as it is executed >> with "Floating exception" on another Linux machine. >> The 2 machines have a similar processors (Intel Core Duo >> and Intel Xeon). >> >> What puzzles me is that it was working properly >> with my previous machine, which was very similar >> to the new one (Dell D400 -> D420). >> Another change is that I shifted from OCaml 3.08 >> to OCaml 3.09. >> >> Does anybody have an idea of the cause of such an >> obscure error ? and how to solve it ? :-) > > Hello, > > just my 2 cents but if you want useful feedback > (or any feedback at all) on your issue, you need to be more specific. > What would help: > - what your program does > - what libraries it is linked to (with their version too) > - your hardware (e.g. your graphic card if your program uses opengl...) > - your distro, its version and its flavour (for both systems e.g. Ubuntu > Gutsy amd64). > - which version of OCaml and how it was installed (via packages, via > godi, by hand,...). > - maybe which drivers your are using if it is relevant (again if you use > opengl, misbehaviour can be caused by many things: drivers, X, opengl > libs, interaction between drivers and your kernel, use of a compositing > manager such as compiz,...) > > - Maybe a stripped down, minimal code sample which reproduces your bug > (if possible). > > Hopefully by gathering all this you will spot the bug yourself :-). > If not then you can ask the list again, with the relevant information. > > Hope this helps,