This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: cc1 aborts with SIGSEGV
- To: spatz at sparrow dot s dot bawue dot de
- Subject: Re: cc1 aborts with SIGSEGV
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Thu, 5 Oct 2000 02:10:56 -0400 (EDT)
- CC: aoliva at redhat dot com, gcc-bugs at gcc dot gnu dot org
- References: <200010042054.e94KsT801396@sparrow.linux.cp>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Wed, 4 Oct 2000 22:54:29 +0200
> From: Christian Pfannschmidt <spatz@sparrow.s.bawue.de>
>
> On October 03 Alexandre Oliva <aoliva@redhat.com> wrote
>
> > This very often indicates hardware problem. There's no source of
> > randomness in GCC that would cause it to randomly crash or succeed
> > when presented the same sources.
>
> Thanks for your advice. It seems, that indeed my (new) mainboard is
> broken. Since I switched off the cache memory, anything works fine,
> though more slowly :-(
This usually means that the main memory is the culprit (it doesn't
keep up with the CPU and the bus). Make sure you didn't buy the
memory chips from the lowest bidder ;-) and replace them if you can.
Also, turning off the CPU cache is not always required. Some boards
have several options for the cache operation mode, so switching to a
less aggressive mode, like from write-behind to write-through, might
help you get reasonable performance without the crashes. The CMOS
setup program is where you change these things.