From: Eli Zaretskii <eliz@gnu.org>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH]: MI -var-set-format
Date: Fri, 25 Jan 2008 10:38:00 -0000 [thread overview]
Message-ID: <uodbamdjc.fsf@gnu.org> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04290E62@ecamlmw720.eamcs.ericsson.se> (marc.khouzam@ericsson.com)
> Date: Thu, 24 Jan 2008 16:35:19 -0500
> From: "Marc Khouzam" <marc.khouzam@ericsson.com>
>
> Index: doc/gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.459
> diff -u -r1.459 gdb.texinfo
> --- doc/gdb.texinfo 23 Jan 2008 11:26:29 -0000 1.459
> +++ doc/gdb.texinfo 24 Jan 2008 21:32:51 -0000
> @@ -20058,6 +20058,9 @@
> recommended to use the @samp{--all-values} option, to reduce the
> number of MI commands needed on each program stop.
>
> +To know if a variable object or any of its children has changed value in any
> +format instead of only the current one, the variable object and all its children
> +should be in the natural format before issuing the @code{-var-update} command.
Sorry, I don't understand what this sentence is trying to say. What
does it mean ``the object should be in the natural format before
issuing the command''? How can an object ``be'' in some format? And
how would its format help me know that it changed its value?
What am I missing here?
next prev parent reply other threads:[~2008-01-25 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 21:49 Marc Khouzam
2008-01-25 10:38 ` Eli Zaretskii [this message]
2008-01-25 15:46 ` Marc Khouzam
-- strict thread matches above, loose matches on Subject: below --
2006-05-02 6:19 Nick Roberts
2006-05-05 18:11 ` Daniel Jacobowitz
2006-05-05 23:30 ` Nick Roberts
2006-05-15 17:07 ` Daniel Jacobowitz
2006-05-16 3:46 ` Nick Roberts
2008-01-22 20:13 ` Daniel Jacobowitz
2008-01-23 3:25 ` Nick Roberts
2008-01-23 3:48 ` Daniel Jacobowitz
2008-01-23 6:24 ` Nick Roberts
2008-01-23 13:17 ` Daniel Jacobowitz
2008-01-23 21:17 ` Nick Roberts
2008-01-23 21:24 ` Daniel Jacobowitz
2008-01-23 22:30 ` Nick Roberts
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=uodbamdjc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.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