public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/18417] New: printing of std::cerr gets "warning: RTTI symbol for class 'std::iostream' has bad type"
Date: Fri, 15 May 2015 19:46:00 -0000	[thread overview]
Message-ID: <bug-18417-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=18417

            Bug ID: 18417
           Summary: printing of std::cerr gets "warning: RTTI symbol for
                    class 'std::iostream' has bad type"
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com
  Target Milestone: ---

this is a corollary to PR 18141.
18141 is a perf issue, this one is for the correctness issue.

"p std::cerr" can give the following:

warning: RTTI symbol for class 'std::iostream' has bad type

this is because the minsym for the vtable is a typedef.

gnuv3_rtti_type calls check_typedef on the value's type,
and then does a minsym lookup by pc for the vtable
which returns "_ZTVSo" which demangles as
"vtable for std::ostream", and "std::iostream" is a typedef.

patch to follow.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2015-05-15 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 19:46 dje at google dot com [this message]
2015-05-27  0:26 ` [Bug c++/18417] " dje at google 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=bug-18417-4717@http.sourceware.org/bugzilla/ \
    --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: 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).