This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: doco patch (was: "[RFA 2/2] Varobj support for Ada.")
> I suggest [...]
> The rest is fine, thanks.
Thanks, Eli. I made the corrections you suggested (thanks!).
For the record, here is the new version of the patch.
--
Joel
>From 0a0c833253a254e5d0ba91c12e369ae5467e59c2 Mon Sep 17 00:00:00 2001
From: Joel Brobecker <brobecker@adacore.com>
Date: Fri, 16 Mar 2012 17:58:08 -0700
Subject: [PATCH] [doco] document the "type_changed" flag further.
gdb/doc/ChangeLog:
* gdb.texinfo (GDB/MI Variable Objects): Document what happens
to the children of a varobj and its update range when -var-update
returns that the varobj's type changed.
---
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 56bf5d5..da1644a 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -29287,6 +29287,12 @@ This is only present if the varobj is still valid. If the type
changed, then this will be the string @samp{true}; otherwise it will
be @samp{false}.
+When a varobj's type changes, its children are also likely to have
+become incorrect. Therefore, the varobj's children are automatically
+deleted when this attribute is @samp{true}. Also, the varobj's update
+range, when set using the @code{-var-set-update-range} command, is
+unset.
+
@item new_type
If the varobj's type changed, then this field will be present and will
hold the new type.
--
1.7.1