From: Andreas Schwab <schwab@linux-m68k.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [4/5] implement "info vtable"
Date: Fri, 20 Jul 2012 08:33:00 -0000 [thread overview]
Message-ID: <m2394mq1cf.fsf@igel.home> (raw)
In-Reply-To: <878vefznvz.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 19 Jul 2012 11:01:04 -0600")
I'm still seeing these failures:
info vtbl e.
vtable for 'E' @ 0x100138e8 (subobject @ 0x100145b0):.
[0]: @0x100142c0: 0x10001b90 <E::f()>.
[1]: @0x10014308: 0x10001c0c <E::vg()>.
[2]: @0x10014368: 0x10001ce8 <E::vv()>.
.
vtable for 'D' @ 0x10013918 (subobject @ 0x100145c0):.
[0]: @0x100142f0: 0x10001c04 <._ZThn16_N1E2vgEv>.
[1]: @0x10014398: 0x10001d8c <D::vd()>.
.
vtable for 'V' @ 0x10013960 (subobject @ 0x100145e0):.
[0]: @0x100143c8: 0x10001e14 <VB::vvb()>.
[1]: @0x10014350: 0x10001cd8 <._ZTv0_n32_N1E2vvEv>.
(gdb) FAIL: gdb.cp/virtfunc.exp: info vtbl e
info vtbl pEe.
vtable for 'E' @ 0x100138e8 (subobject @ 0x100145b0):.
[0]: @0x100142c0: 0x10001b90 <E::f()>.
[1]: @0x10014308: 0x10001c0c <E::vg()>.
[2]: @0x10014368: 0x10001ce8 <E::vv()>.
.
vtable for 'D' @ 0x10013918 (subobject @ 0x100145c0):.
[0]: @0x100142f0: 0x10001c04 <._ZThn16_N1E2vgEv>.
[1]: @0x10014398: 0x10001d8c <D::vd()>.
.
vtable for 'V' @ 0x10013960 (subobject @ 0x100145e0):.
[0]: @0x100143c8: 0x10001e14 <VB::vvb()>.
[1]: @0x10014350: 0x10001cd8 <._ZTv0_n32_N1E2vvEv>.
(gdb) FAIL: gdb.cp/virtfunc.exp: info vtbl pEe
step.
0x0000000010001c04 in ._ZThn16_N1E2vgEv () at ../../../gdb/gdb/testsuite/gdb.cp/virtfunc.cc:203.
203 int D::vg() {return 100+d;}.
(gdb) FAIL: gdb.cp/virtfunc.exp: step through thunk into E::vg
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-07-20 8:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 21:48 Tom Tromey
2012-02-29 18:20 ` Eli Zaretskii
2012-03-01 14:52 ` Pedro Alves
2012-03-01 17:36 ` Tom Tromey
2012-03-01 20:18 ` Pedro Alves
2012-03-15 15:43 ` Tom Tromey
2012-03-16 8:10 ` Crash regression [Re: [4/5] implement "info vtable"] Jan Kratochvil
2012-03-19 18:13 ` Tom Tromey
2012-07-19 9:34 ` [4/5] implement "info vtable" Andreas Schwab
2012-07-19 17:01 ` Tom Tromey
2012-07-20 8:33 ` Andreas Schwab [this message]
2012-07-20 14:24 ` Tom Tromey
2012-07-20 14:29 ` Andreas Schwab
2012-07-20 16:23 ` Tom Tromey
2012-07-20 17:34 ` Andreas Schwab
2012-07-20 17:48 ` Tom Tromey
2012-07-20 18:08 ` Andreas Schwab
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=m2394mq1cf.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@redhat.com \
/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