darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

[doco] document the "type_changed" flag further.

Browse source 
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.
This commit is contained in:
Joel Brobecker 2012-03-28 21:31:46 +00:00
parent d32cafc7d5
commit 7191c1399c
2 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
gdb/doc/ChangeLog
View file

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

6
gdb/doc/gdb.texinfo
View file

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