From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 1/2] gdb-gdb.py: Make the fields copy-paste friendly
Date: Fri, 15 Jan 2010 19:49:00 -0000 [thread overview]
Message-ID: <m36373cfn4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100115192840.GB4324@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Fri, 15 Jan 2010 20:28:40 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> (gdb) p *(struct type *) 0x1dfabf0
Jan> But such printing should be probably more integrated into the framework if
Jan> approved than doing it this way in each case.
Maybe a new option like "set print type" or "set print pointer-type"?
Then it could apply everywhere, not just to the gdb-specific
pretty-printers.
Jan> - fields.append("main_type = %s" % self.val['main_type'])
Jan> + fields.append("main_type = (%s) %s" % (self.val['main_type'].type, self.val['main_type']))
... and in conjunction, changing this to just return values rather than
doing the formatting by hand.
Tom
next prev parent reply other threads:[~2010-01-15 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 19:28 Jan Kratochvil
2010-01-15 19:49 ` Tom Tromey [this message]
2010-01-15 19:56 ` 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=m36373cfn4.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@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