public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/55231] New: ICE in output_addr_table_entry, at dwarf2out.c:21782 with -gsplit-dwarf Date: Wed, 07 Nov 2012 12:11:00 -0000 [thread overview] Message-ID: <bug-55231-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55231 Bug #: 55231 Summary: ICE in output_addr_table_entry, at dwarf2out.c:21782 with -gsplit-dwarf Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: markus@trippelsdorf.de markus@x4 ~ % cat test.ii const char a[] = "split debug doesn't work"; markus@x4 ~ % c++ -c -Og -gsplit-dwarf test.ii test.ii:1:44: internal compiler error: in output_addr_table_entry, at dwarf2out.c:21782 const char a[] = "split debug doesn't work"; ^ 0x690f7b output_addr_table_entry /home/markus/gcc/gcc/dwarf2out.c:21781 0xccd9c7 htab_traverse_noresize /home/markus/gcc/libiberty/hashtab.c:784 0x6baf8a output_addr_table /home/markus/gcc/gcc/dwarf2out.c:21822 0x6baf8a dwarf2out_finish /home/markus/gcc/gcc/dwarf2out.c:23531 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. markus@x4 ~ % c++ -c -O0 -gsplit-dwarf test.ii markus@x4 ~ %
next reply other threads:[~2012-11-07 12:11 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-07 12:11 markus at trippelsdorf dot de [this message] 2012-11-07 12:31 ` [Bug debug/55231] " markus at trippelsdorf dot de 2012-11-15 0:19 ` ccoutant at gcc dot gnu.org 2012-11-15 0:35 ` ccoutant 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-55231-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: 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).