public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/10787: Segmentation fault during the upgrade from gcc2.95.3 to gcc3.2.3
Date: Wed, 14 May 2003 17:56:00 -0000	[thread overview]
Message-ID: <20030514175601.27244.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/10787; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
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
 


             reply	other threads:[~2003-05-14 17:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 17:56 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 20:59 bangerth
2003-05-14 17:36 gm1981

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030514175601.27244.qmail@sources.redhat.com \
    --to=dhazeghi@yahoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).