public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/50006] New: [4.7 Regression] ICE in in connect_traces, at dwarf2cfi.c:2677
Date: Sat, 06 Aug 2011 15:19:00 -0000	[thread overview]
Message-ID: <bug-50006-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50006

           Summary: [4.7 Regression] ICE in in connect_traces, at
                    dwarf2cfi.c:2677
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: danglin@gcc.gnu.org
                CC: rth@gcc.gnu.org
              Host: hppa2.0w-hp-hpux11.11
            Target: hppa2.0w-hp-hpux11.11
             Build: hppa2.0w-hp-hpux11.11


/test/gnu/gcc/objdir/./gcc/xgcc -B/test/gnu/gcc/objdir/./gcc/
-B/opt/gnu/gcc/gcc
-4.7/hppa2.0w-hp-hpux11.11/bin/
-B/opt/gnu/gcc/gcc-4.7/hppa2.0w-hp-hpux11.11/lib
/ -isystem /opt/gnu/gcc/gcc-4.7/hppa2.0w-hp-hpux11.11/include -isystem
/opt/gnu/
gcc/gcc-4.7/hppa2.0w-hp-hpux11.11/sys-include    -c -g -O2  -fPIC
-frandom-seed=
fixed-seed  -W -Wall -gnatpg   s-os_lib.adb -o s-os_lib.o
+===========================GNAT BUG DETECTED==============================+
| 4.7.0 20110805 (experimental) [trunk revision 177484] (hppa2.0w-hp-hpux11.11) 
GCC error:|
| in connect_traces, at dwarf2cfi.c:2677                                   |
| Error detected around s-os_lib.adb:897:8                                 |
| 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).                   |
+==========================================================================+


             reply	other threads:[~2011-08-06 15:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06 15:19 danglin at gcc dot gnu.org [this message]
2011-08-08  9:51 ` [Bug debug/50006] " rguenth at gcc dot gnu.org
2011-08-08 13:01 ` danglin at gcc dot gnu.org
2011-08-08 13:26 ` danglin at gcc dot gnu.org
2011-08-08 21:53 ` rth at gcc dot gnu.org
2011-08-08 22:13 ` dave.anglin at bell dot net
2011-08-08 23:06 ` dave.anglin at bell dot net
2011-08-12 21:28 ` rth at gcc dot gnu.org
2011-08-12 22:03 ` rth at gcc dot gnu.org
2011-08-13  1:28 ` dave.anglin at bell dot net
2011-08-13 21:34 ` danglin at gcc dot gnu.org
2011-08-13 22:01 ` danglin at gcc dot gnu.org
2011-08-15 17:42 ` rth at gcc dot gnu.org
2011-08-15 17:45 ` rth at gcc dot gnu.org
2011-08-15 19:39 ` rth at gcc dot gnu.org
2011-10-06 22:36 ` rth at gcc dot gnu.org

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-50006-4@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).