Re: [Caml-list] Floating exception

[Sebastien Ferre <Sebastien.Ferre@irisa.fr>]

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,