public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bauhaus@futureapps.de To: gcc-gnats@gcc.gnu.org Subject: ada/10356: GNAT BUG DETECTED box Date: Tue, 08 Apr 2003 23:06:00 -0000 [thread overview] Message-ID: <20030408230450.7030.qmail@sources.redhat.com> (raw) >Number: 10356 >Category: ada >Synopsis: GNAT BUG DETECTED box >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Apr 08 23:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: bauhaus@futureapps.de >Release: gcc version 3.2.3 20030309 (Debian prerelease) >Organization: >Environment: Debian GNU/Linux (testing), i86 Linux strudel 2.4.18-xfs #3 Wed Aug 21 20:30:45 CEST 2002 i686 unknown unknown >Description: $ gnatmake e gcc-3.2 -c e.adb +===========================GNAT BUG DETECTED==============================+ | 3.2.3 20030309 (prerelease) (i386-pc-linux-gnu) Gigi abort, Code=104 | | Error detected at e.adb:7:20 | | Please submit a bug report, see http://gcc.gnu.org/bugs.html. | | Include the entire contents of this bug box in the report. | | Include the exact gcc-3.2 or gnatmake command that you entered. | | Also include sources listed below in gnatchop format | | (concatenated together with no headers between files). | +==========================================================================+ Please include these source files with error report e.adb cmd.ads compilation abandoned gnatmake: "e.adb" compilation error Compilation exited abnormally with code 4 at Wed Apr 9 00:22:08 >How-To-Repeat: gnatmake e >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/x-wais-source; name="problem.src" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="problem.src" d2l0aCBjbWQ7Cgpwcm9jZWR1cmUgZSBpcwoKICAgdXNlIGNtZDsKYmVnaW4KICAgZXhlY3YoY21k X25hbWUsIGFyZ3MpOwplbmQgZTsKd2l0aCBJbnRlcmZhY2VzLkMuU3RyaW5nczsgIHVzZSBJbnRl cmZhY2VzLkMuU3RyaW5nczsKCnBhY2thZ2UgQ21kIGlzCgogICBjbWRfbmFtZTogY29uc3RhbnQg Y2hhcnNfcHRyOwogICBwcmFnbWEgSW1wb3J0KEMsIGNtZF9uYW1lKTsKCiAgIGFyZ3M6IGNvbnN0 YW50IGNoYXJzX3B0cl9hcnJheTsKICAgcHJhZ21hIEltcG9ydChDLCBhcmdzKTsKCiAgIHByb2Nl ZHVyZSBleGVjdgogICAgIChmaWxlbmFtZTogaW4gY2hhcnNfcHRyOyBhcmd2OiBpbiBjaGFyc19w dHJfYXJyYXkpOwogICBwcmFnbWEgSW1wb3J0KEMsIGV4ZWN2KTsKCmVuZCBDbWQ7Cg==
next reply other threads:[~2003-04-08 23:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-08 23:06 bauhaus [this message] 2003-05-12 7:36 Dara Hazeghi 2003-05-12 8:36 Dara Hazeghi
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=20030408230450.7030.qmail@sources.redhat.com \ --to=bauhaus@futureapps.de \ --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).