public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/45048] New: duplicate DW_TAG_variable Date: Fri, 23 Jul 2010 17:54:00 -0000 [thread overview] Message-ID: <bug-45048-360@http.gcc.gnu.org/bugzilla/> (raw) Consider this test case: namespace S { int i = 24; int f() { extern int i; return i; } }; When I compile this with g++ svn head (as of a few days ago) I see a duplicate DW_TAG_variable: <2><3d>: Abbrev Number: 4 (DW_TAG_variable) <3e> DW_AT_name : i <40> DW_AT_decl_file : 1 <41> DW_AT_decl_line : 6 <42> DW_AT_MIPS_linkage_name: (indirect string, offset: 0xb): _ZN1S1iE <46> DW_AT_type : <0x5c> <4a> DW_AT_external : 1 <4b> DW_AT_declaration : 1 <2><4c>: Abbrev Number: 4 (DW_TAG_variable) <4d> DW_AT_name : i <4f> DW_AT_decl_file : 1 <50> DW_AT_decl_line : 3 <51> DW_AT_MIPS_linkage_name: (indirect string, offset: 0xb): _ZN1S1iE <55> DW_AT_type : <0x5c> <59> DW_AT_external : 1 <5a> DW_AT_declaration : 1 I think the first one is bogus, given its line number. -- Summary: duplicate DW_TAG_variable Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tromey at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45048
next reply other threads:[~2010-07-23 17:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-23 17:54 tromey at gcc dot gnu dot org [this message] 2010-07-23 21:06 ` [Bug debug/45048] " tromey at gcc dot gnu dot org 2010-07-27 10:40 ` jakub at gcc dot gnu dot org 2010-07-27 11:14 ` jakub at gcc dot gnu dot 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-45048-360@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).