From: Keith Seitz <keiths@redhat.com>
To: Jan Kratochvil <jan.kratochvil@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 17:14:00 -0000 [thread overview]
Message-ID: <4ABF9D6E.8020606@redhat.com> (raw)
In-Reply-To: <20090927122147.GA15789@host0.dyn.jankratochvil.net>
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?
> (2) A lookup can succeed in both "off" and "on" cases with different results.
Indeed. I believe gdb should stick to the language rules, "print object"
or not. We need to break the unwritten gdb development rule that
everything must have a freakin' switch in the debugger. It's
unscalable/unmanageable/user-unfriendly. IMO, "object print" should not
even exist at all.
Keith
next prev parent reply other threads:[~2009-09-27 17:14 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 [this message]
2009-09-27 18:26 ` Jan Kratochvil
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=4ABF9D6E.8020606@redhat.com \
--to=keiths@redhat.com \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@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).