From owner-freebsd-current Wed May 1 12:56:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from neptune.he.net (neptune.he.net [216.218.166.2]) by hub.freebsd.org (Postfix) with ESMTP id 543EE37B41C for ; Wed, 1 May 2002 12:55:59 -0700 (PDT) Received: from borges (stalwart.codysbooks.com [209.133.54.175]) by neptune.he.net (8.8.6/8.8.2) with ESMTP id MAA18570; Wed, 1 May 2002 12:55:56 -0700 Subject: Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 From: Fluid Reply-To: sreese@codysbooks.com To: Ian Cc: freebsd-current In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 01 May 2002 12:52:51 -0700 Message-Id: <1020282771.29023.17.camel@borges.codysbooks.com> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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