From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23697 invoked by alias); 15 Apr 2007 10:35:28 -0000 Received: (qmail 23688 invoked by uid 22791); 15 Apr 2007 10:35:27 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 15 Apr 2007 11:35:25 +0100 Received: (qmail 11762 invoked from network); 15 Apr 2007 10:35:22 -0000 Received: from unknown (HELO ?172.16.64.38?) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 15 Apr 2007 10:35:22 -0000 From: Vladimir Prus To: Eli Zaretskii Subject: Re: Ping: frozen variable objects Date: Sun, 15 Apr 2007 11:42:00 -0000 User-Agent: KMail/1.9.1 Cc: drow@false.org, gdb-patches@sources.redhat.com References: <200703251351.43195.vladimir@codesourcery.com> <200704141353.51962.vladimir@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_k/fIGoo76miu/nE" Message-Id: <200704151435.16838.vladimir@codesourcery.com> 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-04/txt/msg00235.txt.bz2 --Boundary-00=_k/fIGoo76miu/nE Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-length: 841 On Saturday 14 April 2007 22:50, Eli Zaretskii wrote: > > From: Vladimir Prus > > Date: Sat, 14 Apr 2007 13:53:51 +0400 > > Cc: drow@false.org, gdb-patches@sources.redhat.com > > > > Here's what I've just checked in. There was already -var-update anchor, but > > it was on the list of varobj attributes, so I've renamed it, and added -var-update > > anchor at the top of -var-update description. > > Thanks. > > > +@smallexample > > + -var-set-frozen @var{name} @samp{flag} > > +@end smallexample > > + > > +Set the frozeness flag on the variable object @var{name}. The > > +@var{flag} parameter should be either @samp{1} to make the variable > > ``flag'' should be in @var in the example as well, not only in the > text. Here's an editorial patch based on comments from you, Dan and Nick. OK? - Volodya --Boundary-00=_k/fIGoo76miu/nE Content-Type: text/x-diff; charset="iso-8859-15"; name="edits.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="edits.diff" Content-length: 2341 Index: gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.403 diff -u -p -r1.403 gdb.texinfo --- gdb.texinfo 14 Apr 2007 09:51:29 -0000 1.403 +++ gdb.texinfo 15 Apr 2007 10:34:14 -0000 @@ -17296,7 +17296,7 @@ New fields may be added to the output of @item The range of values for fields with specified values, e.g., -@code{in_scope} (@pxref{-var-update-fields}) may be extended. +@code{in_scope} (@pxref{-var-update fields}) may be extended. @c The format of field's content e.g type prefix, may change so parse it @c at your own risk. Yes, in general? @@ -19564,7 +19564,8 @@ list of variable objects whose values ha be a root variable object. Here, ``changed'' means that the result of @code{-var-evaluate-expression} before and after the @code{-var-update} is different. If @samp{*} is used as the variable -object names, all existing variable objects are updated. The option +object names, all existing variable objects are updated, except +for frozen ones (@pxref{-var-set-frozen}). The option @var{print-values} determines whether both names and values, or just names are printed. The possible values of this options are the same as for @code{-var-list-children} (@pxref{-var-list-children}). It is @@ -19585,7 +19586,7 @@ type_changed="false"@}] (gdb) @end smallexample -@anchor{-var-update-fields} +@anchor{-var-update fields} The field in_scope may take three values: @table @code @@ -19610,16 +19611,17 @@ be prepared for this possibility. @xref @subheading The @code{-var-set-frozen} Command @findex -var-set-frozen +@anchor{-var-set-frozen} @subsubheading Synopsis @smallexample - -var-set-frozen @var{name} @samp{flag} + -var-set-frozen @var{name} @var{flag} @end smallexample -Set the frozeness flag on the variable object @var{name}. The +Set the frozenness flag on the variable object @var{name}. The @var{flag} parameter should be either @samp{1} to make the variable -frozen or @samp{0} to make it unfozen. If a variable object is +frozen or @samp{0} to make it unfrozen. If a variable object is frozen, then neither itself, nor any of its children, are implicitly updated by @code{-var-update} (@pxref{-var-update}) of a parent variable or by @code{-var-update *}. Only --Boundary-00=_k/fIGoo76miu/nE--