X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Has NE1 Encountered... Date: 10 Dec 2001 11:29:30 GMT Organization: Aachen University of Technology (RWTH) Lines: 29 Message-ID: <9v26aq$h7i$1@nets3.rz.RWTH-Aachen.DE> References: NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1007983770 17650 137.226.32.75 (10 Dec 2001 11:29:30 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 10 Dec 2001 11:29:30 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com 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.