From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15299 invoked by alias); 20 Sep 2009 15:52:13 -0000 Received: (qmail 15289 invoked by uid 22791); 20 Sep 2009 15:52:12 -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; Sun, 20 Sep 2009 15:52:09 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 1CD442BABBB; Sun, 20 Sep 2009 11:52:08 -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 bgMGjeycjyQX; Sun, 20 Sep 2009 11:52:08 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id D4B022BAB2F; Sun, 20 Sep 2009 11:52:07 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id CD524F5935; Sun, 20 Sep 2009 08:51:54 -0700 (PDT) Date: Sun, 20 Sep 2009 15:52:00 -0000 From: Joel Brobecker To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: Symbols/blocks questions Message-ID: <20090920155154.GS7961@adacore.com> References: <200909191552.02677.ghost@cs.msu.su> <200909192041.14173.ghost@cs.msu.su> <20090919170155.GO7961@adacore.com> <200909192235.37739.ghost@cs.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909192235.37739.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/msg00244.txt.bz2 > Well, string rendition is not really a challenge. You take > struct block *, and then use phex :-) The id need not be > stable across debug sessions, it just should be stable within > one debug session. OK - I just thought that you wanted the user to be able to identify these blocks from the source code. The same way we do when doing (gdb) print FUNC::VAR If you think people will be happy with an arbitrary block ID, then indeed, that's easy (it's actually how task IDs are identified in VxWorks, it's the address of the TCB). -- Joel