[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.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 2a4238b..885b46b 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2012-03-28  Joel Brobecker  <brobecker@adacore.com>
+
+       * 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.
+
 2012-03-27  Jan Kratochvil  <jan.kratochvil@redhat.com>
 
        * gdb.texinfo (Auto-loading): Move @menu to the end of @node.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index aa8bc7c..8002429 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -29382,6 +29382,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.