This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] New maintenance print typechain command.
- From: lode lathouwers <lathouwers_lode at yahoo dot co dot uk>
- To: gdb-patches at sourceware dot org
- Date: Sun, 8 Apr 2007 18:51:46 +0000 (GMT)
- Subject: Re: [PATCH] New maintenance print typechain command.
On Wed, Apr 04, 2007 at 02:37:18PM +0000, lode lathouwers wrote:
> hi
> this is my first patch ever to an open source project , so probably I am doing some things wrong here ...
> Anyway attached you find some changes to add an extra print typechain command, which is like typechain, but instead of printing the internal nodes in the raw format it prints them in c-format.
> This is handy when we want to extract some type declarations from a series of headerfiles, and generate a header file only containing the declarations for those types. Afterwards, we could for example use the file in swig to generate interfaces towards other programming languages.
Do you mean you're parsing the output of the maintenance command
to create your header?
No, the output of the ,maintenance command is directly (via copypaste) used in the header; i.e. the output is a series of pure c(++) declarations,
so no parsing is needed.
I think that's a bad idea; the maint commands
are intended for GDB developers to use while debugging GDB.
Indeed maybe the maintenance group ,might not be the best position to place this command. Maybe something like info typechain might
be better ?
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.
--
Daniel Jacobowitz
CodeSourcery
___________________________________________________________
All New Yahoo! Mail – Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html