Date: 01 May 2002 12:52:51 -0700 From: Fluid <fluid@sfmidimafia.com> To: Ian <freebsd@damnhippie.dyndns.org> Cc: freebsd-current <freebsd-current@FreeBSD.ORG> Subject: Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 Message-ID: <1020282771.29023.17.camel@borges.codysbooks.com> In-Reply-To: <B8F423F9.C842%freebsd@damnhippie.dyndns.org> References: <B8F423F9.C842%freebsd@damnhippie.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2002-04-30 at 10:35, Ian wrote: > > > cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got > > fatal signal 10 > > > > I have seen cc1 die like this many many times, and have only ever seen 2 > root causes for the death: > > 1) bad ram > 2) you overclocked the cpu or bus just a bit too much How about signal 4? I was rebuilding my -current the other day and I kept getting mostly signal 4 errors (in different places) with a couple of signal 10's and 11's. I tried finding a run-down of what the various errors meant, but I couldn't find a thing. The weird thing is that when I switched terminals in KDE (i.e. opened a new Konsole window), my build problems ceased. Windows XP runs on the same box with no problems (i.e. will run for weeks without a reboot) so I'm a little hesitant to blame my hardware. -Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1020282771.29023.17.camel>