From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14301 invoked by alias); 5 Dec 2002 17:17:25 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 14282 invoked by uid 61); 5 Dec 2002 17:17:25 -0000 Date: Thu, 05 Dec 2002 09:17:00 -0000 Message-ID: <20021205171725.14281.qmail@sources.redhat.com> To: dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: ehrhardt@mathematik.uni-ulm.de Reply-To: ehrhardt@mathematik.uni-ulm.de, dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: other/8822: internal error segmentation fault X-SW-Source: 2002-12/txt/msg00281.txt.bz2 List-Id: Synopsis: internal error segmentation fault State-Changed-From-To: open->feedback State-Changed-By: cae State-Changed-When: Thu Dec 5 09:17:22 2002 State-Changed-Why: This is most likely a hardware problem with your machine. Try to run memtest and try to replace your RAM chips. To do anything useful with this report we'll need a preprocessed source file that reproducible causes the compiler to crash on your machine. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8822