From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15952 invoked by alias); 5 Jan 2007 09:04:37 -0000 Received: (qmail 15943 invoked by uid 22791); 5 Jan 2007 09:04:36 -0000 X-Spam-Check-By: sourceware.org Received: from zigzag.lvk.cs.msu.su (HELO zigzag.lvk.cs.msu.su) (158.250.17.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 05 Jan 2007 09:04:32 +0000 Received: from Debian-exim by zigzag.lvk.cs.msu.su with spam-scanned (Exim 4.50) id 1H2l00-00075X-Nx for gdb-patches@sources.redhat.com; Fri, 05 Jan 2007 12:04:29 +0300 Received: from localhost ([127.0.0.1] helo=ip6-localhost) by zigzag.lvk.cs.msu.su with esmtp (Exim 4.50) id 1H2kzr-0006jG-Sc; Fri, 05 Jan 2007 12:04:19 +0300 From: Vladimir Prus Subject: Re: variable objects and registers To: Nick Roberts , gdb-patches@sources.redhat.com Date: Fri, 05 Jan 2007 09:04:00 -0000 References: <17782.41205.881283.845357@kahikatea.snap.net.nz> <17802.17932.377094.90049@kahikatea.snap.net.nz> User-Agent: KNode/0.10.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Message-Id: 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: 2007-01/txt/msg00176.txt.bz2 Nick Roberts wrote: > > > > I've settled on -var-list. I don't think 'create' clarifies much, > > > > and this is not user command, > > > > > > Except that it doesn't just list existing variable objects but > > > "creates" new ones. > > > > I fact, I'm not sure what duplicated > > > > -var-list --locals > > > > should do. Create afresh, or just return already created? > > Thats a fair point. It should only create new variable objects if > execution > enters a new block. That makes -var-list a reasonable name. In the > manual I should have said "...creates variable objects for the children if > they do not already exist.". Yeah. For -var-list, I've modified the manual to say that -var-list tries to return previously-created varobjs. For -var-list --registers I did not implement such reusing logic, because I feel it's not very important performance-wise (yet?). For -var-list --locals, we'll certainly have reuse of previously-created varobj, though. - Volodya