From owner-freebsd-current Tue Apr 30 15:24:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from forrie.ne.client2.attbi.com (forrie.ne.client2.attbi.com [24.147.156.140]) by hub.freebsd.org (Postfix) with ESMTP id 34C3A37B41D for ; Tue, 30 Apr 2002 15:24:13 -0700 (PDT) Received: from boom.forrie.com (internal-23.forrie.net. [192.168.1.23]) by forrie.ne.client2.attbi.com with id g3UMOAg74757 for ; Tue, 30 Apr 2002 18:24:11 -0400 (EDT) Message-Id: <5.1.0.14.2.20020430182241.05713968@192.168.1.1> X-Sender: forrie@192.168.1.1 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 30 Apr 2002 18:24:14 -0400 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) 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 I've experienced this same problem today; but only after installing 5.0-current on the system in question. It compiled fine with FreeBSD_4.5. This is a 1.2ghz Pentium with 1gb of RAM. No problems with other things (large compile projects with 4.5 before). _F > From: "Jose M. Alcaide" > Date: Tue, 30 Apr 2002 11:28:48 +0200 > To: current@FreeBSD.ORG > Subject: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 > > I am getting this error while building XFree86-Server-4.2.0_2 on a > recently updated -CURRENT (Mon Apr 29 10:55:43 GMT): > > [snip] > > 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 cc1 dying on a long complex source module when you've overclocked beyond what your silicon can handle is so reliable a test that it's the first thing I use when trying to find the true speed a new system will run at. If you're not overclocking, then bad ram would make a good second suspect, I had a failing DIMM a couple years ago first manifest as signal 10 and 11 errors in cc1. -- Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message