From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13279 invoked by alias); 29 Mar 2005 20:37:39 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12819 invoked from network); 29 Mar 2005 20:37:25 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 29 Mar 2005 20:37:25 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DGNTq-0005QZ-GL for ; Tue, 29 Mar 2005 15:38:30 -0500 Date: Tue, 29 Mar 2005 20:37:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sources.redhat.com Subject: Re: RFC: Print the type of a C value in one more case Message-ID: <20050329203830.GA20646@nevyn.them.org> Mail-Followup-To: gdb-patches@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00380.txt.bz2 On Tue, Mar 29, 2005 at 12:13:14AM -0500, Paul Schlie wrote: > >> Daniel Jacobowitz wrote: > >> This is something that constantly bugs me when debugging GCC. GCC has > >> typedefs for "tree" and "rtx" which are both pointers to structs. When > >> you print either, you just get "$1 = 0xbf000100" without any indication > >> of the type of the variable; but normally GDB prints types for pointers. > >> This comes from a missing check_typedef in c_value_print. > >> > >> There were a couple of ways to fix it; I chose to print the typedef rather > >> than what the typedef pointed to. The only difference in the testsuite is > >> in one objc test, which perfectly illustrates the desired change: > >> > >> -$1 = 0x0 > >> +$1 = (id) 0x0 > >> ... > > - was there ever a conclusion on this item, it certainly seems helpful? I never got around to committing it. Since no one disliked it, I've checked this in now. -- Daniel Jacobowitz CodeSourcery, LLC