This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Document fixed/floating variable objects and thread-id.
- From: Daniel Jacobowitz <drow at false dot org>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Fri, 4 Apr 2008 08:07:35 -0400
- Subject: Re: [RFA] Document fixed/floating variable objects and thread-id.
- References: <200804041320.00361.vladimir@codesourcery.com>
On Fri, Apr 04, 2008 at 01:20:00PM +0400, Vladimir Prus wrote:
>
> This patch adds some more docs about variable objects. Even
> though floating variable objects have know bugs, I think their
> intended behaviour is sufficiently clear right now to document.
>
> - Volodya
>
> * gdb/doc/gdb.texinfo (gdb/mi Variable object): Document
> fixed and floating variable objects, and clarify that
> a variable object can also be found to a thread. Update
> -var-create example.
There's also this patch, if you want to grab any text from it:
http://sourceware.org/ml/gdb-patches/2007-05/msg00397.html
I noticed that he used "@@", which is probably correct; you had
"@" and I think texinfo will take that as an operator.
> -unique provided that one does not specify @var{name} on that format.
> -The command fails if a duplicate name is found.
> +unique provided that one does not explicitly specifies @var{name} of
> +that format. The command fails if a duplicate name is found.
>
"specify" from the original text was correct; "on" was not, nice catch.
> The frame under which the expression should be evaluated can be
> specified by @var{frame-addr}. A @samp{*} indicates that the current
> -frame should be used.
> +frame should be used. A @samp{*} indicates that a floating variable
> +object must be created.
Two spaces.
--
Daniel Jacobowitz
CodeSourcery