Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [mi] [ada] varobjs for registers 2
Date: Wed, 20 Dec 2006 19:44:00 -0000	[thread overview]
Message-ID: <utzzql5d9.fsf@gnu.org> (raw)
In-Reply-To: <200612202137.29038.vladimir@codesourcery.com> (message from 	Vladimir Prus on Wed, 20 Dec 2006 21:37:28 +0300)

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Wed, 20 Dec 2006 21:37:28 +0300
> 
> This is a second revision of the patch to add MI command that
> creates varobjs for registers. The command is renamed to -var-list
> and used like:
> 
> 	-var-list --registers
> 
> There are now docs and tests. The created variable objects no longer
> have 'public' pseudo-fields, no matter what the language of the program is.
> 
> Along the way, I've promoted a private function in ada-lang.c to language.c,
> so I'd appreciate if Ada maintainers take a quick look.
> 
> OK?

Thanks.

The patch for the manual is approved, but please take care of these
minor problems:

> +This command is intended to efficiently create a number of variable
> +objects---for example for registers, or for local variables.  Using 
> +the @code{-var-create} command would not be ideal, because it must be
> +issued once for every variable object.

Please add a cross-reference to the description of -var-create here.

> +be used with caution, as gdb can determine the value in the parent
                            ^^^
Please use @value{GDBN}.

> +The MI result record includes the @samp{result} field which value is
                                                         ^^^^^^
"whose value is..."

> +a list of tuples.  Each tuple describes a single variable object in
> +the same was as for the @code{-var-create} command:
   ^^^^^^^^^^^^^^^^^^^
Something's wrong here.

> +@smallexample
> +^done,registers=[{name="var1",exp="$eax",numchild="0",value="16",type="int"},....
> +@end smallexample

This line is too long for @smallexample, please break it into two
lines.


  reply	other threads:[~2006-12-20 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 18:38 Vladimir Prus
2006-12-20 19:44 ` Eli Zaretskii [this message]
2007-01-05  9:01   ` Vladimir Prus
2007-01-05  9:29     ` Eli Zaretskii
2006-12-21  7:20 ` Joel Brobecker
2006-12-30 20:30   ` Daniel Jacobowitz
2007-01-05  9:06     ` Vladimir Prus
2007-01-05 10:24       ` Nick Roberts
2007-01-05 10:47         ` Vladimir Prus

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=utzzql5d9.fsf@gnu.org \
    --to=eliz@gnu.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