public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "André Pönitz" <andre.poenitz@nokia.com>
To: gdb@sourceware.org
Cc: ext Klaus Rudolph <lts-rudolph@gmx.de>
Subject: Re: automated cast to different data type possible?
Date: Mon, 16 May 2011 11:43:00 -0000	[thread overview]
Message-ID: <201105161343.54594.andre.poenitz@nokia.com> (raw)
In-Reply-To: <4DCFE110.4000703@gmx.de>

On Sunday 15 May 2011 16:20:00 ext Klaus Rudolph wrote:
> André Pönitz wrote:
>
> > Assuming that I understood the task correctly it can be done with 
> > gdb python scripting nevertheless. [...It] 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]
> 
> Sorry,
> 
> please give me an idea who is calling qdump_KRBase and what is parameter
> d? I actually have no idea how to add that to the printer script... or
> maybe any other python script to gdb.

The code would be called from a Python script that creates the full
display for an local variable including all expanded children in one go. 
'd' is an object that accumulates output that's finally 'printed', and
takes care of properly closing nested items in case of exceptions.

The approach is different from the one taken by the "official" pretty 
printers, but also uses gdb's python scripting. Since this approach
gives access to all levels of the hierarchy at one time, re-arranging
items or re-writing parts of the "parent" items (like in your case the 
name of the type) is straightforward.

Andre'

  reply	other threads:[~2011-05-16 11:43 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
2011-05-15 14:17         ` Klaus Rudolph
2011-05-16 11:43           ` André Pönitz [this message]
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=201105161343.54594.andre.poenitz@nokia.com \
    --to=andre.poenitz@nokia.com \
    --cc=gdb@sourceware.org \
    --cc=lts-rudolph@gmx.de \
    /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).