From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7288 invoked by alias); 25 Nov 2005 03:07:35 -0000 Received: (qmail 7280 invoked by uid 22791); 25 Nov 2005 03:07:35 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 25 Nov 2005 03:07:34 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EfTvw-0005EY-AT; Thu, 24 Nov 2005 22:07:32 -0500 Date: Fri, 25 Nov 2005 03:09:00 -0000 From: Daniel Jacobowitz To: Stefan =?iso-8859-1?Q?Burstr=F6m?= Cc: gdb@sources.redhat.com Subject: Re: info types question Message-ID: <20051125030732.GB20073@nevyn.them.org> Mail-Followup-To: Stefan =?iso-8859-1?Q?Burstr=F6m?= , gdb@sources.redhat.com References: <20051122232047.GA32223@nevyn.them.org> <347779088c4.4f532204@mail.m.bonet.se> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <347779088c4.4f532204@mail.m.bonet.se> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00552.txt.bz2 On Wed, Nov 23, 2005 at 12:30:44AM +0100, Stefan Burström wrote: > Hello Daniel > > On 2005-11-22, you wrote: > > >> The former I guess doesn't really matter, but the later really defines > >> int to be an unsigned 64 bit type. Which cannot be what is desired? > >> Of course I can ignore all types defined int libgcc2.c but I'd like to > >> find out the 'logic' behind this. > > > > These probably indicate "typedefs" without a name, probably definitions > > of base types. > > I see.I guess this is just the way things are then? Or is there a way for > gdb to figure out if this is a basic type to make sure that it is indicated > in the output? I don't know - probably we can improve it. However... > The reason for this is that I'd like to be able to resolve types into their > basic types when I dump variables in my frontend. Eg, > > typedef char * STRPTR; > STRPTR mystring; > > Would allow me to print the mystring variable as a real string since I can > find out that the type of mystring really is char *. > > Btw, the mi output of info types is broken.Only the name is output, and not > the type. Is this a known issue? ... it sounds like you're using MI, so let's focus on improving the MI output instead. Could you show an example of this problem? -- Daniel Jacobowitz CodeSourcery, LLC