public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "garynot at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/50292] compiler bug box - pl-io.ads
Date: Mon, 05 Sep 2011 04:09:00 -0000 [thread overview]
Message-ID: <bug-50292-4-9p39lBHsMZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50292-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50292
--- Comment #1 from Gary Barnes <garynot at comcast dot net> 2011-09-05 04:09:32 UTC ---
Created attachment 25192
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25192
gnatchop file containing the source
gnatchop format file with the source code causing the bug box.
gcc \
-c \
-gnata \
-gnatE \
-fstack-check \
-gnatef \
-gnatf \
-gnatm50 \
-gnatn \
-gnato \
-gnatU \
-gnatwa \
-gnatwe \
-gnatwi \
-gnatwj \
-gnatwK \
-gnatwl \
-Wuninitialized \
-gnatVa \
-pass-exit-codes \
-O \
-g \
-gnatA \
./pb_code_main.adb
+===========================GNAT BUG DETECTED==============================+
| 4.5.1 20100924 (Red Hat 4.5.1-4) (i686-redhat-linux-gnu) Assert_Failure
sem_ch3.adb:12928|
| Error detected at pl-io.ads:510:9 |
| Please submit a bug report; see http://gcc.gnu.org/bugs.html. |
| 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). |
+==========================================================================+
next prev parent reply other threads:[~2011-09-05 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 4:03 [Bug ada/50292] New: " garynot at comcast dot net
2011-09-05 4:09 ` garynot at comcast dot net [this message]
2011-09-05 4:10 ` [Bug ada/50292] " garynot at comcast dot net
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=bug-50292-4-9p39lBHsMZ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).