From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15641 invoked by alias); 1 Mar 2012 22:58:47 -0000 Received: (qmail 15628 invoked by uid 22791); 1 Mar 2012 22:58:46 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Mar 2012 22:58:31 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id D99711C6C43; Thu, 1 Mar 2012 17:58:30 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zVjJ48gjbXAU; Thu, 1 Mar 2012 17:58:30 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A06CF1C6C42; Thu, 1 Mar 2012 17:58:30 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 3F57E145615; Thu, 1 Mar 2012 14:58:27 -0800 (PST) Date: Thu, 01 Mar 2012 22:58:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: gdb-patches@sourceware.org Subject: Re: [RFA 1/3] language-specific read_var_value for Ada renamings Message-ID: <20120301225827.GC2853@adacore.com> References: <1330546034-27156-1-git-send-email-brobecker@adacore.com> <1330546034-27156-2-git-send-email-brobecker@adacore.com> <87vcmodrqr.fsf@fleche.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87vcmodrqr.fsf@fleche.redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2012-03/txt/msg00054.txt.bz2 > I think the patch is fine, given that we've already gone pretty far down > this road. Awesome, thanks for looking at the patch. > I wonder whether it would be possible to deal with the renaming when > reading symbols. [...] I have thought about this many times in the past. But I am not sure how to do this. At least some of them seem really hard to do. For instance, this issue with renamings: It would seem to me that the way to go would be to translate the textual expression from the symbol name into some kind of location expression. A little like the DWARF locations, but with possible symbol lookups, array subscripting, taking record components, etc. In this case, I'd rather continue pushing for standard DWARF, and just get rid of the encoding altogether... -- Joel