From: Daniel Jacobowitz <drow@false.org>
To: lode lathouwers <lathouwers_lode@yahoo.co.uk>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] New maintenance print typechain command.
Date: Tue, 10 Apr 2007 14:03:00 -0000 [thread overview]
Message-ID: <20070410140254.GA30086@caradoc.them.org> (raw)
In-Reply-To: <108445.72375.qm@web28004.mail.ukl.yahoo.com>
On Sun, Apr 08, 2007 at 06:51:46PM +0000, lode lathouwers wrote:
> Why can't you get what you need from 'info types'?
> Info types does not show complete struct declarations (fields are not shown) Also it gives ALL type names,
> while I only want to explore/print a few + their downward dependancies.
>
So what you want is the output of ptype for a bunch of different
types, but you don't know in advance which. I think we should wait a
little while; our plan for this year (well, my plan anyway) is to add
Python scripting support to GDB, and that will be powerful enough to
do this. I don't think the command will be widely enough useful to
implement it in GDB proper.
Once we have Python support, though, we should include a directory of
contributed and example scripts - this would be a great start for that.
(I'm planning to work on this starting in a month or so.)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-10 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 18:51 lode lathouwers
2007-04-10 14:03 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-04 14:37 lode lathouwers
2007-04-07 17:39 ` Daniel Jacobowitz
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=20070410140254.GA30086@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=lathouwers_lode@yahoo.co.uk \
/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