From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 2/2] Doc 'dynamic' for command -var-list-children
Date: Tue, 19 Nov 2013 11:31:00 -0000 [thread overview]
Message-ID: <1384860516-6949-2-git-send-email-yao@codesourcery.com> (raw)
In-Reply-To: <1384860516-6949-1-git-send-email-yao@codesourcery.com>
Hi,
I find "dynamic=1" appear in the result of each child of the output of
-var-list-children,
-var-list-children ss1
^done,numchild="2",children=[child={name="ss1.a",exp="a",numchild="0",type="struct s",thread-id="1",dynamic="1"},child={name="ss1.b",exp="b",numchild="0",type="struct s",thread-id="1",dynamic="1"}],has_more="0"
but the doc doesn't mention this. This patch is to copy the description
of "dynamic=1" here.
gdb/doc:
2013-11-19 Yao Qi <yao@codesourcery.com>
* gdb.texinfo (GDB/MI Variable Objects): Add attribute 'dynamic'
for the output of command -var-list-children.
---
gdb/doc/gdb.texinfo | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 0f6046d..04fcb7b 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -32522,6 +32522,11 @@ A dynamic varobj can supply a display hint to the front end. The
value comes directly from the Python pretty-printer object's
@code{display_hint} method. @xref{Pretty Printing API}.
+@item dynamic
+This attribute will be present and have the value @samp{1} if the
+varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
+then this attribute will not be present.
+
@end table
The result has its own attribute:
--
1.7.7.6
next prev parent reply other threads:[~2013-11-19 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 11:39 [PATCH 1/2] Update doc on displayhint in " Yao Qi
2013-11-19 11:31 ` Yao Qi [this message]
2013-11-19 16:17 ` [PATCH 2/2] Doc 'dynamic' for " Eli Zaretskii
2013-11-21 3:52 ` Yao Qi
2013-11-19 16:22 ` [PATCH 1/2] Update doc on displayhint in " Eli Zaretskii
2013-11-19 17:05 ` Tom Tromey
2013-11-20 2:16 ` Yao Qi
2013-11-22 20:02 ` Tom Tromey
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=1384860516-6949-2-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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