[12/14] Mention virtual tables in Python dynamic_type documentation
Commit Message
PR python/16461 asks that the Python dynamic_type documentation
mention virtual tables; this patch implements that request.
gdb/doc/ChangeLog
2018-09-08 Tom Tromey <tom@tromey.com>
PR python/16461:
* python.texi (Values From Inferior): Mention use of virtual
table.
---
gdb/doc/ChangeLog | 6 ++++++
gdb/doc/python.texi | 16 ++++++++--------
2 files changed, 14 insertions(+), 8 deletions(-)
Comments
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Sat, 8 Sep 2018 14:14:15 -0600
>
> PR python/16461 asks that the Python dynamic_type documentation
> mention virtual tables; this patch implements that request.
>
> gdb/doc/ChangeLog
> 2018-09-08 Tom Tromey <tom@tromey.com>
>
> PR python/16461:
> * python.texi (Values From Inferior): Mention use of virtual
> table.
OK, thanks.
@@ -658,14 +658,14 @@ The type of this @code{gdb.Value}. The value of this attribute is a
@end defvar
@defvar Value.dynamic_type
-The dynamic type of this @code{gdb.Value}. This uses C@t{++} run-time
-type information (@acronym{RTTI}) to determine the dynamic type of the
-value. If this value is of class type, it will return the class in
-which the value is embedded, if any. If this value is of pointer or
-reference to a class type, it will compute the dynamic type of the
-referenced object, and return a pointer or reference to that type,
-respectively. In all other cases, it will return the value's static
-type.
+The dynamic type of this @code{gdb.Value}. This uses the object's
+virtual table and the C@t{++} run-time type information
+(@acronym{RTTI}) to determine the dynamic type of the value. If this
+value is of class type, it will return the class in which the value is
+embedded, if any. If this value is of pointer or reference to a class
+type, it will compute the dynamic type of the referenced object, and
+return a pointer or reference to that type, respectively. In all
+other cases, it will return the value's static type.
Note that this feature will only work when debugging a C@t{++} program
that includes @acronym{RTTI} for the object in question. Otherwise,