From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15093 invoked by alias); 17 Feb 2006 20:32:32 -0000 Received: (qmail 15083 invoked by uid 22791); 17 Feb 2006 20:32:31 -0000 X-Spam-Check-By: sourceware.org Received: from wsip-24-248-2-174.ph.ph.cox.net (HELO public.ninemoons.com) (24.248.2.174) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Feb 2006 20:32:30 +0000 Received: from puffer.diveadx.com (dpc67446126.direcpc.com [67.44.6.126]) by public.ninemoons.com (8.13.4/8.13.4) with ESMTP id k1HKVCtT028965; Fri, 17 Feb 2006 13:31:18 -0700 Received: from [192.168.1.146] (unknown [192.168.1.146]) by puffer.diveadx.com (Postfix) with ESMTP id DDEF3297320; Fri, 17 Feb 2006 15:48:26 -0500 (EST) From: Fred Fish Reply-To: fnf@diveadx.com To: Eli Zaretskii Subject: Re: [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units Date: Fri, 17 Feb 2006 20:32:00 -0000 User-Agent: KMail/1.9.1 Cc: drow@false.org, jimb@red-bean.com, gdb-patches@sourceware.org, fnf@specifix.com References: <200601031517.50309.fnf@specifix.com> <200602161916.00761.fnf@diveadx.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602171531.27812.fnf@diveadx.com> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00337.txt.bz2 On Friday 17 February 2006 04:15, Eli Zaretskii wrote: > Will the manual's description of the differences between these two > commands be still valid after this change? Here is a patch for the doc change. If there aren't any objections, I'd like to get this patch and the code/testsuite patch checked in ASAP and get back to work on the parser change to accept the 'file'::typename syntax. -Fred 2006-02-17 Fred Fish * gdb.texinfo (Symbols): Update descriptions of 'whatis' and 'ptype' commands to reflect the fact that the only significant difference between them is that ptype prints the complete type description instead of just the name. Index: gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.313 diff -c -p -r1.313 gdb.texinfo *** gdb.texinfo 10 Feb 2006 03:54:33 -0000 1.313 --- gdb.texinfo 17 Feb 2006 20:26:04 -0000 *************** it to find out the name of a variable or *** 10364,10389 **** @kindex whatis @item whatis @var{expr} ! Print the data type of expression @var{expr}. @var{expr} is not ! actually evaluated, and any side-effecting operations (such as ! assignments or function calls) inside it do not take place. @xref{Expressions, ,Expressions}. - @item whatis - Print the data type of @code{$}, the last value in the value history. - @kindex ptype - @item ptype @var{typename} - Print a description of data type @var{typename}. @var{typename} may be - the name of a type, or for C code it may have the form @samp{class - @var{class-name}}, @samp{struct @var{struct-tag}}, @samp{union - @var{union-tag}} or @samp{enum @var{enum-tag}}. - @item ptype @var{expr} @itemx ptype ! Print a description of the type of expression @var{expr}. @code{ptype} ! differs from @code{whatis} by printing a detailed description, instead ! of just the name of the type. For example, for this variable declaration: --- 10364,10388 ---- @kindex whatis @item whatis @var{expr} ! @itemx whatis @var{typename} ! @itemx whatis ! Print the data type of expression @var{expr} or type @var{typename}. ! @var{expr} is not actually evaluated, and any side-effecting operations ! (such as assignments or function calls) inside it do not take place. ! @var{typename} may be the name of a type or typedef, or for C code it may ! have the form @samp{class @var{class-name}}, @samp{struct @var{struct-tag}}, ! @samp{union @var{union-tag}} or @samp{enum @var{enum-tag}}. ! Without any arguments, print the data type of @code{$}, the last value ! in the value history. @xref{Expressions, ,Expressions}. @kindex ptype @item ptype @var{expr} + @itemx ptype @var{typename} @itemx ptype ! @code{ptype} accepts the same arguments as @code{whatis}, but prints a ! detailed description of the type, instead of just the name of the type. ! @xref{Expressions, ,Expressions}. For example, for this variable declaration: