Date:	Mon, 22 Jan 2001 17:47:54 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Tom St Denis <stdenis AT compmore DOT net>
cc:	djgpp AT delorie DOT com
Subject:	Re: DJGPP in ms-dos prompt (under win98)
In-Reply-To:	<94hadq$d27$1@nnrp1.deja.com>
Message-ID:	<Pine.SUN.3.91.1010122174148.28597B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 22 Jan 2001, Tom St Denis wrote:

> My previous machine was a AMD K6-II.  This is an Athlon.
> 
> > If not, what is different with this machine?  If this is the same
> > machine where previous builds succeeded, what changed since the last
> > successful build?
> 
> Um I have four times the memory now, a faster cpu, and a larger hard disk. 

If this is a new machine, I'd suspect a hardware problem as the most 
probable cause.  Inconsistent crashes usually mean that some memory chip 
is faulty or does not keep up with the CPU and the bus.  GCC catches such 
problems quite often, because it's a memory hog, moves large buffers to 
and fro, and runs the CPU at full throttle for prolonged periods of time.

If the CPU is overclocked, turn that off and see if that helps.  If the 
CPU cache(s) are set to some aggressive mode, such as write-back, change 
that to less aggressive mode and see if that helps.  If the problem 
persists even with vanilla settings of these parameters, get a 
replacement for your hardware.

> Well I get those bugs during every compile.  To be honest I think it's my
> computer, cuz I get "internal compiler errors" in MSVC too.

This is yet another sign that the hardware is the reason.

- Raw text -