From owner-freebsd-current Sat May 27 15:32:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 8BAF337B642 for ; Sat, 27 May 2000 15:32:29 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id PAA77777; Sat, 27 May 2000 15:35:40 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200005272235.PAA77777@troutmask.apl.washington.edu> Subject: Re: Internal compiler error: program ld got fatal signal 10 In-Reply-To: <39303CEA.C0958F14@buckhorn.net> from Bob Martin at "May 27, 2000 04:23:54 pm" To: Bob Martin Date: Sat, 27 May 2000 15:35:40 -0700 (PDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Martin wrote: > > with "unsubscribe freebsd-current" in the body of the message > If you are using an older K6 with more than 32mb of ram, this will > happen from time to time of it's own accord. I have never taken the time > to find out why, but if you search the archives, you will find that it > happens quite a bit. > SMP Pentium Pro with 256 MB of memory, and only scsi hardware. Note, ld is getting a signal 10 (SIGBUS) not signal 11 (SIGSEGV), which is the typical crappy hardware signal. Also, I can build the world as long as I use sources older that 23 May 00. This leads me to believe that the new binutils are having some problems. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message