From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16860 invoked by alias); 3 Apr 2009 16:30:39 -0000 Received: (qmail 16845 invoked by uid 22791); 3 Apr 2009 16:30:34 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 03 Apr 2009 16:30:27 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 6BC4E10DD7; Fri, 3 Apr 2009 16:30:25 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 4BD1F106A7; Fri, 3 Apr 2009 16:30:25 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1LpmHg-00005P-I8; Fri, 03 Apr 2009 12:30:24 -0400 Date: Fri, 03 Apr 2009 16:30:00 -0000 From: Daniel Jacobowitz To: Tom Tromey Cc: gdb-patches@sourceware.org Subject: Re: Python pretty-printing [3/6] Message-ID: <20090403163024.GB28512@caradoc.them.org> Mail-Followup-To: Tom Tromey , gdb-patches@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) 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: 2009-04/txt/msg00072.txt.bz2 On Thu, Apr 02, 2009 at 02:55:41PM -0600, Tom Tromey wrote: > * Values From Inferior:: > +* Types From Inferior:: Python representation of types. This isn't entirely a new problem, as you can see from context above, but is there anything we can call this besides "From Inferior"? Types don't come from an inferior, they come from a program or an object file. > +The following methods are provided: > + > +@table @code > +@defmethod Type Type [name] > +Construct a new instance of @code{gdb.Type}. > + > +If @var{name} is given, it specifies the name of a type to look up in > +the inferior. @var{name} is searched for globally. > +@end defmethod So the constructor does a lookup. This will be a little weird if we want to create types from scratch someday (could be very useful). And what happens if name is not given? Anyway, I wonder if there shouldn't be an explicit lookup routine instead. > +@findex TYPE_CODE_FLAGS > +@findex gdb.TYPE_CODE_FLAGS > +@item TYPE_CODE_FLAGS > +A bit flags type. > +@c FIXME: what is this? It's used for the x86 status register, for instance. Try info reg eflags. It's more friendly than just a number (although I do get user complaints about it; could be friendlier). > +@findex TYPE_CODE_TEMPLATE > +@findex gdb.TYPE_CODE_TEMPLATE > +@item TYPE_CODE_TEMPLATE > +A C++ template type. Note that this is not used for a template > +instantiation; those appear as ordinary struct types. > +@c FIXME I hope that is true DWARF does not represent TYPE_CODE_TEMPLATE, as far as I know. This was used by the HP symbol reader. It looks like nothing in GDB currently creates these and they could be garbage collected (with optional reimplementation later). > +@findex TYPE_CODE_TEMPLATE_ARG > +@findex gdb.TYPE_CODE_TEMPLATE_ARG > +@item TYPE_CODE_TEMPLATE_ARG > +A C++ template argument. > +@c FIXME: is this ever used? No, see above. -- Daniel Jacobowitz CodeSourcery