Re: Compiler errors...

[Jason Downs <downsj@downsj.com>]

In message <199805312332.RAA27589@xerxes.courtesan.com>,
	"Todd C. Miller" writes:
>This is usually indicative of a memory problem.  If you don't have
>parity memory it may mean you have a bad simm (if you have parity
>and parity checking turned on you would get an NMI on a parity error).
>Try making the memory timings as pessimistic as possible.

Actually, in the case of Pentium and Cyrix CPUs, it's also indicative of
a corrupt L1 cache.  i.e., the chip is running too fast.

Bad memory usually doesn't restrain itself to acting up only when you run
a large process.

--
Jason Downs		   (360) 694-3110
downsj@downsj.com