This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/13735] New: set print vtbl bugs
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 23 Feb 2012 21:59:24 +0000
- Subject: [Bug c++/13735] New: set print vtbl bugs
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13735
Bug #: 13735
Summary: set print vtbl bugs
Product: gdb
Version: 7.4
Status: NEW
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned@sourceware.org
ReportedBy: tromey@redhat.com
Classification: Unclassified
Right now 'set print vtbl' doesn't do much of value.
It seems to print just a single vtable entry.
There does not seem to be a very good way to
determine the size of the vtable from the information
we have available.
All I can think of is that we could examine all the
methods in the current class, compute their vtable offsets,
and then use this to determine the maximum vtable size.
(Perhaps with some hand-waving around virtual bases, I haven't
considered that far.)
A few other comments --
It would be nice to rename this to "set print vtable", as "vtbl"
is unnecessarily terse.
It would be nice to have an "info vtable EXPR" command, to avoid
dealing with stuff like 'print a.'_vtbl_A'.
The documentation needs some updating in this area.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.