public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: drow@mvista.com To: gcc-gnats@gcc.gnu.org Subject: c++/10499: [3.2, 3.3, 3.4] Debug information for some C++ headers is missing classes (template specific?) Date: Fri, 25 Apr 2003 14:36:00 -0000 [thread overview] Message-ID: <20030425143253.21010.qmail@sources.redhat.com> (raw) >Number: 10499 >Category: c++ >Synopsis: [3.2, 3.3, 3.4] Debug information for some C++ headers is missing classes (template specific?) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Apr 25 14:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: drow@mvista.com >Release: 3.4 20030308, 3.3 cvs, 3.2.3 >Organization: >Environment: i686-pc-linux-gnu >Description: Compile this testcase (from Ben Kosnik) with -g: #include <sstream> int main() { std::stringstream s; // (gdb) p s return 0; } Look in the debug info for information about stringstream. In DWARF-2 (the problem is also visible in stabs+) this is all there is: <3><ef9>: Abbrev Number: 17 (DW_TAG_typedef) DW_AT_name : (indirect string, offset: 0xddd): stringstream DW_AT_decl_file : 3 DW_AT_decl_line : 144 DW_AT_type : <f13> <1><f13>: Abbrev Number: 13 (DW_TAG_structure_type) DW_AT_name : (indirect string, offset: 0x7b9): basic_stringstream<char,std::char_traits<char>,std::allocator<char> > DW_AT_declaration : 1 i.e just a declaration. Also in 3.4, the typedef is emitted in the DW_TAG_lexical_block associated with main. That doesn't make a whole lot of sense and will eventually confuse GDB. >How-To-Repeat: Compile above testcase with -g >Fix: The debug information for the body of basic_stringstream needs to be emitted. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-04-25 14:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030425143253.21010.qmail@sources.redhat.com \ --to=drow@mvista.com \ --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).