Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Document fixed/floating variable objects and thread-id.
Date: Fri, 04 Apr 2008 13:08:00 -0000	[thread overview]
Message-ID: <20080404120735.GA5549@caradoc.them.org> (raw)
In-Reply-To: <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


  parent reply	other threads:[~2008-04-04 12:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04  9:32 Vladimir Prus
2008-04-04 11:47 ` Eli Zaretskii
2008-04-09 13:49   ` Vladimir Prus
2008-04-09 15:21     ` Eli Zaretskii
2008-04-09 17:06       ` Vladimir Prus
2008-04-09 18:04         ` Eli Zaretskii
2008-04-09 20:37           ` Vladimir Prus
2008-04-09 21:25             ` Eli Zaretskii
2008-04-09 22:17               ` Vladimir Prus
2008-04-23 11:52                 ` Vladimir Prus
2008-04-23 18:00                   ` Eli Zaretskii
2008-04-26 17:44                     ` Vladimir Prus
2008-04-26 18:45                       ` Eli Zaretskii
2008-04-04 13:08 ` Daniel Jacobowitz [this message]
2008-04-04 13:44 ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080404120735.GA5549@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox