public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "philippe.waroquiers at skynet dot be" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/15975] New: info vtbl does not produce any information and  set print vtbl on/off has no effect
Date: Mon, 23 Sep 2013 20:46:00 -0000	[thread overview]
Message-ID: <bug-15975-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 15975
           Summary: info vtbl does not produce any information and  set
                    print vtbl on/off has no effect
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: philippe.waroquiers at skynet dot be

Created attachment 7214
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7214&action=edit
leak_cpp_interior.cpp , simple class hierarchy with MI

info vtbl does not produce any information.
It is also unclear what 'set print vtbl on'
should have as an effect: I cannot see any
difference when it is on or off.


g++ -g -o leak_cpp_interior leak_cpp_interior.cpp
gdb ./leak_cpp_interior
break 40
run
...
p *ptrBC
$1 = {_vptr.B = 0x80489d8 <vtable for C+24>}
(gdb) info vtbl ptrBC
(gdb) info vtbl *ptrBC
(gdb) set print vtbl on
(gdb) p *ptrBC
$2 = {_vptr.B = 0x80489d8 <vtable for C+24>}
(gdb) p *ptrAC
$3 = {_vptr.A = 0x80489c8 <vtable for C+8>}
(gdb) info vtbl ptrAC
(gdb) info vtbl *ptrAC
(gdb) 

Tested on f12/x86, gdb7.6, 
Same behaviour on ppc64 gcc110 (gdb 7.6, gcc 4.7.2)
and on amc64 gcc20 ((gdb 7.6, gcc 4.4.5).

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


                 reply	other threads:[~2013-09-23 20:46 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=bug-15975-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).