This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/2] Update doc on displayhint in command -var-list-children
- From: Yao Qi <yao at codesourcery dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Wed, 20 Nov 2013 08:37:57 +0800
- Subject: Re: [PATCH 1/2] Update doc on displayhint in command -var-list-children
- Authentication-results: sourceware.org; auth=none
- References: <1384860516-6949-1-git-send-email-yao at codesourcery dot com> <87iovomjwn dot fsf at fleche dot redhat dot com>
On 11/20/2013 12:32 AM, Tom Tromey wrote:
> If a varobj has a pretty-printer, then the display hint is an attribute
> of that printer. It ought to be printed as an attribute of the result.
>
> Of course, child objects can have their own pretty-printers, and thus
> their own display hints.
How about adding the description of "displayhint" in child result?
--
Yao (éå)
gdb/doc:
2013-11-20 Yao Qi <yao@codesourcery.com>
* gdb.texinfo (GDB/MI Variable Objects): Add the description
of "displayhint" to the table about child results.
---
gdb/doc/gdb.texinfo | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 19e9aa5..d26cd0e 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -32516,6 +32516,12 @@ Otherwise this result is not present.
@item frozen
If the variable object is frozen, this variable will be present with a value of 1.
+
+@item displayhint
+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}.
+
@end table
The result may have its own attributes:
--
1.7.7.6