From: Joel Brobecker Date: Wed, 28 Mar 2012 21:31:46 +0000 (+0000) Subject: [doco] document the "type_changed" flag further. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=7191c1399c5435c5b08be03c76ad4299371fc516;p=binutils-gdb.git [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 2a4238bc06f..885b46bf548 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,9 @@ +2012-03-28 Joel Brobecker + + * 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 * gdb.texinfo (Auto-loading): Move @menu to the end of @node. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index aa8bc7c83b5..8002429b599 100644 --- 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.