From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19411 invoked by alias); 29 Mar 2005 05:13:23 -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 19250 invoked from network); 29 Mar 2005 05:13:17 -0000 Received: from unknown (HELO rwcrmhc14.comcast.net) (216.148.227.89) by sourceware.org with SMTP; 29 Mar 2005 05:13:17 -0000 Received: from [10.0.1.2] (c-24-61-199-96.hsd1.nh.comcast.net[24.61.199.96]) by comcast.net (rwcrmhc14) with SMTP id <2005032905131601400bvvlne>; Tue, 29 Mar 2005 05:13:16 +0000 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Tue, 29 Mar 2005 05:13:00 -0000 Subject: Re: RFC: Print the type of a C value in one more case From: Paul Schlie To: Daniel Jacobowitz CC: Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-SW-Source: 2005-03/txt/msg00371.txt.bz2 >> 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?