From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1873 invoked by alias); 19 Sep 2009 17:02:17 -0000 Received: (qmail 1770 invoked by uid 22791); 19 Sep 2009 17:02:14 -0000 X-SWARE-Spam-Status: No, hits=-2.4 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; Sat, 19 Sep 2009 17:02:08 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 5905C2BAB38; Sat, 19 Sep 2009 13:02:07 -0400 (EDT) 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 lTPCLVzeKKDh; Sat, 19 Sep 2009 13:02:07 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 18DF02BAB1A; Sat, 19 Sep 2009 13:02:07 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 688FDF5935; Sat, 19 Sep 2009 10:01:55 -0700 (PDT) Date: Sat, 19 Sep 2009 17:02:00 -0000 From: Joel Brobecker To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: Symbols/blocks questions Message-ID: <20090919170155.GO7961@adacore.com> References: <200909191552.02677.ghost@cs.msu.su> <20090919163344.GL7961@adacore.com> <200909192041.14173.ghost@cs.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909192041.14173.ghost@cs.msu.su> User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00237.txt.bz2 > Then, it's probably likewise not true for any other random address > in block. And then, the only reliable way to identify a block is via > its address. I think that's correct. We have routines IIRC that locate the innermost block for a PC, or something like that, but I don't think we identify blocks by their start address... > What I'm trying to do is make -stack-list-variables output block > together with a name of variable, and make -var-create accept > some block specification. This, together, should all to display ^^^allow ? > shadowed variables in frontend. Looks like 'block' should be > the string rendition of the address of struct block :-/ Depending on the language, lexical blocks can be named, and it looks like DWARF supports that, so I suppose you could you that. But blocks can definitely be annonymous too, in which case the "string rendition" might be a challenge... -- Joel