public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "andre dot poenitz at nokia dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/11639] New: Base class type information not accessible in binaries compiled with g++ 4.5.0 Date: Wed, 26 May 2010 15:05:00 -0000 [thread overview] Message-ID: <20100526150538.11639.andre.poenitz@nokia.com> (raw) This is the "second issue" in http://sourceware.org/bugzilla/show_bug.cgi?id=10953 but as it seems unrelated I put it as a separate issue here: If 'Derived' and 'Base' are setup as in #10953, and there is an additional function 'Derived::foo()' with the following implementation void Derived::foo() { Base *b = this; Base &br = *b; } then 'print b' yields "$1 = (void *) 0xbfffee38", i.e. the type information for 'b' is completely lost. It should print (Base *) 0xbfffee38. The problem is not present in g++ 4.4. -- Summary: Base class type information not accessible in binaries compiled with g++ 4.5.0 Product: gdb Version: 7.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned at sourceware dot org ReportedBy: andre dot poenitz at nokia dot com CC: gdb-prs at sourceware dot org GCC build triplet: i486-linux-gnu GCC host triplet: i486-linux-gnu GCC target triplet: i486-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=11639 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-05-26 15:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-26 15:05 andre dot poenitz at nokia dot com [this message] 2010-05-26 15:15 ` [Bug gdb/11639] " andre dot poenitz at nokia dot com 2010-08-18 20:19 ` tromey at redhat dot com 2010-08-19 6:59 ` andre dot poenitz at nokia dot com
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=20100526150538.11639.andre.poenitz@nokia.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).