From owner-freebsd-current Mon Dec 20 9: 1:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 20EA615333 for ; Mon, 20 Dec 1999 09:01:13 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id MAA17492; Mon, 20 Dec 1999 12:00:22 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id MAA27900; Mon, 20 Dec 1999 12:00:04 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id MAA81313; Mon, 20 Dec 1999 12:00:04 -0500 (EST) Date: Mon, 20 Dec 1999 12:00:04 -0500 (EST) From: Thomas David Rivers Message-Id: <199912201700.MAA81313@lakes.dignus.com> To: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com, rivers@dignus.com Subject: Re: cc taking a signal 11 In-Reply-To: <199912201652.LAA01812@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Nawww... I've tried this on a bunch of different machines.. as a matter > of fact it replicates with gcc version 2.7.2.1 from December of last > year. I find it hard to believe that I have 80 machines that all > exhibit the exact same memory failure... :-) > > -John > > > Yep - others have reported the problem is gcc... I'd suggest taking this up with Cygnus (http://www.cygnus.com) - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message