From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3104 invoked by alias); 7 Apr 2007 17:39:28 -0000 Received: (qmail 3092 invoked by uid 22791); 7 Apr 2007 17:39:28 -0000 X-Spam-Check-By: sourceware.org Received: from return.false.org (HELO return.false.org) (66.207.162.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 07 Apr 2007 18:39:25 +0100 Received: from return.false.org (localhost [127.0.0.1]) by return.false.org (Postfix) with ESMTP id 685434B267; Sat, 7 Apr 2007 12:39:24 -0500 (CDT) Received: from caradoc.them.org (dsl093-172-095.pit1.dsl.speakeasy.net [66.93.172.95]) by return.false.org (Postfix) with ESMTP id 53C424B262; Sat, 7 Apr 2007 12:39:20 -0500 (CDT) Received: from drow by caradoc.them.org with local (Exim 4.63) (envelope-from ) id 1HaEsh-0006le-SV; Sat, 07 Apr 2007 13:39:19 -0400 Date: Sat, 07 Apr 2007 17:39:00 -0000 From: Daniel Jacobowitz To: lode lathouwers Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] New maintenance print typechain command. Message-ID: <20070407173919.GE24650@caradoc.them.org> Mail-Followup-To: lode lathouwers , gdb-patches@sourceware.org References: <130247.15914.qm@web28011.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <130247.15914.qm@web28011.mail.ukl.yahoo.com> User-Agent: Mutt/1.5.14+cvs20070313 (2007-03-13) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00048.txt.bz2 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? I think that's a bad idea; the maint commands are intended for GDB developers to use while debugging GDB. Why can't you get what you need from 'info types'? -- Daniel Jacobowitz CodeSourcery