From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4108 invoked by alias); 27 Jun 2007 06:30:53 -0000 Received: (qmail 4099 invoked by uid 22791); 27 Jun 2007 06:30:52 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 27 Jun 2007 06:30:49 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1I3R2n-0005cF-IQ for gdb@sources.redhat.com; Wed, 27 Jun 2007 08:30:26 +0200 Received: from 77.246.241.246 ([77.246.241.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Jun 2007 08:30:25 +0200 Received: from ghost by 77.246.241.246 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Jun 2007 08:30:25 +0200 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: [MI] frozen variable objects (bug) Date: Wed, 27 Jun 2007 06:30:00 -0000 Message-ID: References: <18049.38770.289829.412279@kahikatea.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.2 X-IsSubscribed: yes 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: 2007-06/txt/msg00333.txt.bz2 Nick Roberts wrote: > > In principle, if a variable object is frozen, print_varobj prints it's > state out with: > > if (varobj_get_frozen (var)) > ui_out_field_int (uiout, "frozen", 1); > > In practice this never happens because print_varobj is called > > a) from -var-create, in which case the object can only be frozen _after_ > it > is created. Yes. The intention is that future patches will cause varobjs to be created frozen in some cases, without explicit commands from gdb. Said patches got stuck, unfortunately. > b) from -var-list-children, but the frozen flag is not set for children, > only > for the variable object that was explicitly chosen I don't understand what do you mean by "explicitly chosen". Just like -var-create, in current FSF HEAD children varobjs always created non-frozen. You can freeze any children you like. > I guess the front end should keep track of which objects are frozen but > it's an attribute that should/could be added to the MI command > -var-show-attributes. We never established what's the intended use of -var-show-attributes and if that command should be present at all. > Aside: I still don't understand the need for frozen objects. In Emacs, if > I want to disable automatic update of a complex data type, I just click on > the parent to contract the display, which invokes "-var-delete -c" to > delete the > children. If later I want to look at their values, clicking on the parent > regenerates the children. And how do you highlight values that were changed? - Volodya