> > > cc -O2   -o t t.c 
> > > cc: Internal compiler error: program cc1 got fatal signal 11
> > > *** Error code 1
> > 
> > The mysterious sig11 problem...
> > 
> > Read this: http://www.bitwizard.nl/sig11/
> 
> The above link gives a lot of attention to hardware problems, and then, in
> a small note at the bottom:
> 	* No or too little swap space.  Gcc doesn't gracefully handle the
> 	"out of memory" condition.

This is a brand new asus A7V mb with 850MHz athlon, 256Mb memory. Since it
has been running fine for 2 weeks, I thought something might have been 
done in the source tree, and wanted to give a heads up if that was the
case. If I have intermittant hardware of some sort, the rate of occurance
is very low. I recompiled and reinstalled my source tree using an older
install, with no problems to speak of. I am now rebuilding with my normal
configuration to verify it is fixed (the compiler runs now).

As far as hardware failures, I have not seen any decent diagnostics for
motherboards, etc. since I bought my IBM AT system about a decade ago.
Is there a diagnostics resource somewhere that can test out my hardware
under load? Prefferably pointing out the faulty piece of hardware. If 
nothing else, a repeatable hardware failure would allow troubleshooting.

> 
> I don't know about your situation in particular, but every time I received
> signal 11, it was on a machine with very little ram and swap.
> -- 
> Ben Collver -- collver@softhome.net
> Your fellow-man? Divide the epithet: Say rather, you're the fellow, he the man.
> 
> 


-- 
Joseph Sarkes		jsarkes@tiac.net