From owner-freebsd-stable@FreeBSD.ORG Wed May 24 07:42:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A4DA16A573 for ; Wed, 24 May 2006 07:42:07 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 55DC343D8F for ; Wed, 24 May 2006 07:41:55 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 24 May 2006 07:41:54 -0000 Received: from p54A7C76C.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.199.108] by mail.gmx.net (mp035) with SMTP; 24 May 2006 09:41:54 +0200 X-Authenticated: #5465401 Message-ID: <44740E39.8000901@gmx.de> Date: Wed, 24 May 2006 09:41:45 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: Dave References: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> In-Reply-To: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: internal compiler error: segmentation fault: 11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 07:42:07 -0000 Dave wrote: > Hello, > I'm trying to compile 6.0-stable on a release box, prior to upgrade. > I've tried several times and all end with an internal compiler error: > segmentation fault: 11. And then i'm told to submit a bug report. My > problem is when this occurs it's not always at the same spot or the same > file. One time it even core dumped, though only once. > At this point i would appreciate any suggestions, i'm hoping this is > not the indicator of a problem. > Thanks. > Dave. > I'd say in most cases it means that either your memory or your CPU get too hot. Open the case of your machine. If the problem disappears or at least appears less often, consider better cooling for your computer.