From owner-freebsd-bugs@FreeBSD.ORG  Wed Nov 16 22:06:05 2005
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@hub.freebsd.org
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8184C16A421;
	Wed, 16 Nov 2005 22:06:05 +0000 (GMT)
	(envelope-from kris@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3D4E843D45;
	Wed, 16 Nov 2005 22:06:05 +0000 (GMT)
	(envelope-from kris@FreeBSD.org)
Received: from freefall.freebsd.org (kris@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAGM65o4057829;
	Wed, 16 Nov 2005 22:06:05 GMT
	(envelope-from kris@freefall.freebsd.org)
Received: (from kris@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAGM65iK057825;
	Wed, 16 Nov 2005 22:06:05 GMT (envelope-from kris)
Date: Wed, 16 Nov 2005 22:06:05 GMT
From: Kris Kennaway <kris@FreeBSD.org>
Message-Id: <200511162206.jAGM65iK057825@freefall.freebsd.org>
To: wroberts@securenym.net, kris@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc: 
Subject: Re: misc/89103: gcc segmentation fault errors -- ??memory leak?
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2005 22:06:05 -0000

Synopsis: gcc segmentation fault errors -- ??memory leak?

State-Changed-From-To: open->analyzed
State-Changed-By: kris
State-Changed-When: Wed Nov 16 22:03:09 GMT 2005
State-Changed-Why: 
Your observations on memory use are not likely to be relevant unless
your system is running completely out of swap (in which case, that's
your problem).  You are just observing the compiler doing its job by
allocating memory when compiling a file.

Whether or not you believe it, this is almost certainly due to a
hardware failure.  Rule that out in the usual way (swap out RAM, check
CPU cooling, cabling, power supply, etc), and then let us know whether
it persists.

http://www.freebsd.org/cgi/query-pr.cgi?pr=89103