Mail Archives: djgpp/2001/12/10/06:32:55
Radical wrote:
> Ever have the problem using DJGPP 2.95.3/2.03 where either compiling
> a program twice produces different results, or running a program on
> the same exact data produces different results (using methods which
> are definitely expected to produce consistant results)?
Why don't you just tell us what those "methods which are ..." actually
are? Might make debugging a whole lot easier.
For the compiler, the only really "different" result would be a change
of the messages it generates during compilation. Like, say, once it
crashes or reports an error in your source, the next time it doesn't.
Byte differences in the .o files don't count, in that respect ---
those could be timestamps or random garbage copied into the file.
> I just can not understand why this is happening. Running from a
> Win95 dosshell, I've never noticed this this phenonima to be so
> apparent now.
By far the most probable reason is hardware instability, followed by
some bad lowlevel software problem like an incorrect filesystem state
managed by a dum driver. If you added or replaced any piece of
hardware in your system recently, suspect that. Esp. if that hardware
is RAM or a new CPU.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -