From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17633 invoked by alias); 15 Mar 2003 18:49:43 -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 17613 invoked by uid 48); 15 Mar 2003 18:49:42 -0000 Date: Sat, 15 Mar 2003 18:49:00 -0000 Message-ID: <20030315184942.17612.qmail@sources.redhat.com> To: dieter.ferdinand@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: bangerth@dealii.org Reply-To: bangerth@dealii.org, 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: 2003-03/txt/msg01026.txt.bz2 List-Id: Synopsis: internal error segmentation fault State-Changed-From-To: feedback->closed State-Changed-By: bangerth State-Changed-When: Sat Mar 15 18:49:42 2003 State-Changed-Why: Whatever the cause may be, if we are to fix something then we need a _reproducible_ testcase. At any rate, repeated sporadic errors on a widely available system on which gcc is built daily are not enough to describe a bug. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8822