This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Grief with Dejagnu; Testing gcc 2.95.3.test4 on SCO OS5.0.4
- To: dkorn at pixelpower dot com (David Korn)
- Subject: Re: Grief with Dejagnu; Testing gcc 2.95.3.test4 on SCO OS5.0.4
- From: Joe Buck <jbuck at synopsys dot COM>
- Date: Mon, 26 Feb 2001 11:48:25 -0800 (PST)
- Cc: gressett at iglobal dot net ('David Gressett'), gcc at gcc dot gnu dot org
> Yeah, that is the legendary 'erratic signal 11 thing'. Some people think
> it's caused by hardware problems: bad RAM or trouble with the memory timing
> parameters in your bios.
See
http://www.bitwizard.nl/sig11/
for advice on how to determine whether this symptom is a software or a
hardware problem, and, if it is hardware, what might be causing it.
> It crops up under Linux and Cygwin as well, so
> that would suggest it isn't a simple software problem. OTOH you can run a
> memory checker continuously for days on end (I've tried) without spotting
> any errors;
Some memory checkers are much better than others. The one in the PC BIOS
is near-worthless except for detecting that one of your DRAM chips is
completely non-functional.