From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27287 invoked by alias); 14 May 2003 17:56:02 -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 27247 invoked by uid 71); 14 May 2003 17:56:01 -0000 Date: Wed, 14 May 2003 17:56:00 -0000 Message-ID: <20030514175601.27244.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Dara Hazeghi Subject: Re: bootstrap/10787: Segmentation fault during the upgrade from gcc2.95.3 to gcc3.2.3 Reply-To: Dara Hazeghi X-SW-Source: 2003-05/txt/msg01672.txt.bz2 List-Id: The following reply was made to PR bootstrap/10787; it has been noted by GNATS. From: Dara Hazeghi To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, gm1981@libero.it Cc: Subject: Re: bootstrap/10787: Segmentation fault during the upgrade from gcc2.95.3 to gcc3.2.3 Date: Wed, 14 May 2003 10:54:42 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=10787 Hello, you do realize that every e-mail sent to gcc-gnats@gcc.gnu.org with a different subject line becomes a different bug report, right? So you've reported the same bug three times today. Anyway, to get the preprocessed source you add the flag -save-temps to the commandline, and repeat the failing command. The file with the .i suffix is the preprocessed source. Note that to send follow ups to your bug report, you just need to reply to this message (or look it up under GNATS and click e-mail interested parties). Could you please, in addition to the preprocessed source, include the complete command that was failing. I can't tell if this is a failure in stage 1, or 2. Thanks, Dara