From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: archer@sourceware.org
Subject: Re: set print objct pros/cons [Re: [Keith Seitz] Re: [tools-team] Status 2008-09-01]
Date: Sun, 27 Sep 2009 18:26:00 -0000 [thread overview]
Message-ID: <20090927182601.GA10613@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <4ABF9D6E.8020606@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
On Sun, 27 Sep 2009 19:14:22 +0200, Keith Seitz wrote:
> On 09/27/2009 05:21 AM, Jan Kratochvil wrote:
> >
> >(1) Last "call basep->m ()" should have printed "derived::m"
> > because "p basep->m" prints "Derived::m()", shouldn't it?
> >
>
> basep->m will always print "base::m" -- your test case did not
> declare Base::m virtual. Or is that just an omission in the file you
> attached?
It was intentional that way (unaware how common it is in C++ to override
non-virtual method name by a virtual one, though).
I think the following two commands should deal with the same pointer, whithout
even talking about which pointer ("Derived::m" or "Base::m") it should be:
It does not work now - with the previous testcase cxxinherit.C:
(gdb) set print object on
(gdb) p basep->m
$4 = {void (Derived *)} 0x4006c4 <Derived::m()>
(gdb) call basep->m ()
base::m
> IMO, "object print" should not even exist at all.
Currently the "off" mode does not work right for the virtual/virtual case:
With the new attached testcase cxxinherit2.C:
Starting program: /home/jkratoch/t/cxxinherit2
derived::m
derived::m
Breakpoint 1, main () at cxxinherit2.C:27
27 return 0;
(gdb) show print object
Printing of object's derived type based on vtable info is off.
(gdb) call basep->m ()
derived::m
(gdb) p basep->m
$1 = {void (Base *)} 0x4006a6 <Base::m()>
(gdb)
Regards,
Jan
[-- Attachment #2: cxxinherit2.C --]
[-- Type: text/plain, Size: 404 bytes --]
#include <stdio.h>
class Base
{
public:
virtual void m () { puts ("base::m"); }
virtual void stub () {}
};
class Derived : public Base
{
public:
virtual void m () { puts ("derived::m"); }
virtual void stub () {}
};
int
main ()
{
Derived derived_local;
Derived *derivedp = &derived_local;
Base *basep = &derived_local;
derivedp->m ();
basep->m ();
return 0;
}
prev parent reply other threads:[~2009-09-27 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 14:08 [Keith Seitz] Re: [tools-team] Status 2008-09-01 Dragos Tatulea
2009-09-25 18:40 ` Tom Tromey
2009-09-25 19:39 ` Dragos Tatulea
2009-09-25 20:45 ` Tom Tromey
2009-09-27 12:22 ` set print objct pros/cons [Re: [Keith Seitz] Re: [tools-team] Status 2008-09-01] Jan Kratochvil
2009-09-27 17:14 ` Keith Seitz
2009-09-27 18:26 ` Jan Kratochvil [this message]
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=20090927182601.GA10613@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@sourceware.org \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).