Re: Ping: frozen variable objects

Eli Zaretskii
2007-04-13T09:53:33Z

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Wed, 11 Apr 2007 18:43:43 +0400
> Cc: gdb-patches@sources.redhat.com
>
> > Hmm, that line at the bottom says there's detailed documentation
> > below. But you didn't add any for -var-set-frozen.
>
> Wierd, that docs were in previous patch. I've revived them now.

Thanks. I'm okay with the doco patch, after you fix the following
minor problems:

> +leaf variable objects, which always have built-in types. Child variable
^^
Two blanks after a period, please.

> +objects are created only by explicit request, so if a frontend
> +is not interested in children of a particular variable object, no
^^^^^^^^^^^
"in the children"

> +be transferred to the frontend. As noted above, children variable
^^
Two blanks.

> +objects are created on demand, and only leaf variable object have a
^^^^^^^^^^^^^^^^^^^^
"leaf variable objects", in plural.

> +@smallexample
> + -var-set-frozen @var{name} @samp{flag}
> +@end smallexample
> +
> +Set the frozeness flag on the variable object @var{name}. The
> +@samp{flag} parameter should be either @samp{1} to make the variable
> +frozen or @samp{0} to make it unfozen.

Here `flag' stands for something else (0 or 1), so it should be in
@var, not @samp, like `name'.

> If a variable object is
> +frozen, then neither itself, nor any of its children, are
> +implicitly updated by @code{-var-update} of a parent variable or
> +by @code{-var-update *}.

A @pxref here to where -var-update is described would be a good idea.