public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com To: gcc-gnats@gcc.gnu.org Subject: ada/6919: Bug box refers to missing file gnatinfo.txt Date: Mon, 03 Jun 2002 06:26:00 -0000 [thread overview] Message-ID: <20020603131751.15228.qmail@sources.redhat.com> (raw) >Number: 6919 >Category: ada >Synopsis: Bug box refers to missing file gnatinfo.txt >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jun 03 06:26:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: David Billinghurst >Release: 3.2 20020603 (experimental) (i686-pc-cygwin) >Organization: >Environment: i686-pc-cygwin >Description: The ada bug box (below) refers to file gnatinfo.txt, but the file is not in CVS or generated by the build. +===========================GNAT BUG DETECTED==============================+ | 3.2 20020603 (experimental) (i686-pc-cygwin) GCC error: | | internal error: Segmentation fault | | Error detected at /usr/local/src/gcc/gcc/ada/s-except.ads:154:7 | | Please submit bug report by email to gcc-bugs@gcc.gnu.org. | | Use a subject line meaningful to you and us to track the bug. | | Include the entire contents of this bug box in the report. | | Include the exact gcc or gnatmake command that you entered. | | Also include sources listed below in gnatchop format | | (concatenated together with no headers between files). | | (use plain ASCII or MIME attachment). | | See gnatinfo.txt for full info on procedure for submitting bugs. | +==========================================================================+ >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-03 13:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-03 6:26 David.Billinghurst [this message] 2002-06-03 7:56 Joseph S. Myers
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=20020603131751.15228.qmail@sources.redhat.com \ --to=david.billinghurst@riotinto.com \ --cc=gcc-gnats@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: linkBe 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).