compilation on different machines led to different executables

I was provided with the source code and the executable of a numerical
model, which I have to use for my studies.

After compiling the code on my machine I tried to run the executable.
Unfortunately, it stopped due to a "division by zero" forced by a
mistake in the code for special input values equal zero. I do not
encounter this problem with the original executable, although it is
based on the very same code.

Can anyone provide me with an explanation - given the code, compiler
and compiler flags being the same -
1) why the original executable somehow handles the error (division by
zero should always lead to an abort) and
2) why there are different executables when compiling it on different
machines (both windows)?
Solutions or Workarounds are welcome, but I'm mainly interested in a
general explanation.

Thank you for your help.
Jens

.

Relevant Pages

  • Re: How safe is intellectual property in compiled binaries?
    ... > compiling source code into an executable is pre-defined. ... > a compiler destroys information in the compilation process, ... some names make their way into some executables as ...
    (comp.lang.fortran)
  • Re: Modifing existing header file
    ... >>This header file is shared between multiple C files, ... >>compiled into separate executables. ... >>After compiling the ...
    (comp.lang.c)
  • Re: Newbie advice on correct way to debug please
    ... >device immediately quits with no error messages. ... I tried compiling a debug ... answers are likely to be very different for eVC with MFC, ... The "executables" generated by VS.NET are ...
    (microsoft.public.pocketpc.developer)
  • Re: Class names are put into executables !!! ( Tenative Solution )
    ... >>Oliver, please stop telling me what is right or wrong for me. ... >>I don't like the class names in the executables. ... > 3rd party obfuscators available, you could run this over a copy of your ... > production source and then use that for compiling. ...
    (borland.public.delphi.non-technical)
  • Re: compilation on different machines led to different executables
    ... > mistake in the code for special input values equal zero. ... > Can anyone provide me with an explanation - given the code, compiler ... > 2) why there are different executables when compiling it on different ... Windows, other than to use the default IEEE floating point model. ...
    (comp.lang.fortran)