From: "André Pönitz" <andre.poenitz@nokia.com>
To: gdb@sourceware.org
Cc: ext Tom Tromey <tromey@redhat.com>, Klaus Rudolph <lts-rudolph@gmx.de>
Subject: Re: automated cast to different data type possible?
Date: Thu, 12 May 2011 17:13:00 -0000 [thread overview]
Message-ID: <201105121913.12475.andre.poenitz@nokia.com> (raw)
In-Reply-To: <m3k4dvnbuu.fsf@fleche.redhat.com>
On Thursday 12 May 2011 18:05:13 ext Tom Tromey wrote:
> >>>>> "Klaus" == Klaus Rudolph <lts-rudolph@gmx.de> writes:
>
> Tom> You want "set print object on".
>
> Klaus> This only works with classes which includes a vtable, but there
> Klaus> is no virtual function inside that hierarchy.
>
> Sorry about that; you even noted this in your original message and I
> missed it.
>
> Pretty-printers just change how a value is displayed. They don't change
> the type. [...]
Assuming that I understood the task correctly it can be done with
gdb python scripting nevertheless.
Given
struct KRBase
{
enum Type { TYPE_A, TYPE_B } type;
KRBase(Type _type) : type(_type) {}
};
struct KRA : KRBase { int x, y; KRA() : KRBase(TYPE_A), x(1), y(32) {} };
struct KRB : KRBase { KRB() : KRBase(TYPE_B) {} };
void testKR()
{
KRBase *ptr1 = new KRA;
KRBase *ptr2 = new KRB;
break_here();
}
creating a display of
ptr1 @0x809a9d0 KRA
KRBase KRA
x 1 int
y 32 int
ptr2 @0x809a9e0 KRB
KRBase KRB
takes three lines of python code:
def qdump__KRBase(d, item):
base = ["KRA", "KRB"][int(item.value["type"])]
d.putItem(Item(item.value.cast(lookupType(base)), item.iname))
[using, admittedly, the *cough* "other" approach to pretty printing]
Andre'
PS: I put a real screenshot at
http://imageshack.us/photo/my-images/135/kr2e.png
as I am not sure how acceptable attaching a 15k .png is on this list.
next prev parent reply other threads:[~2011-05-12 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 9:09 Klaus Rudolph
2011-05-11 21:00 ` Tom Tromey
2011-05-12 6:17 ` Klaus Rudolph
2011-05-12 16:06 ` Tom Tromey
2011-05-12 17:13 ` André Pönitz [this message]
2011-05-15 14:17 ` Klaus Rudolph
2011-05-16 11:43 ` André Pönitz
2011-05-16 17:15 ` Klaus Rudolph
2011-05-24 13:48 ` André Pönitz
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=201105121913.12475.andre.poenitz@nokia.com \
--to=andre.poenitz@nokia.com \
--cc=gdb@sourceware.org \
--cc=lts-rudolph@gmx.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).