diff options
author | Joel Brobecker <brobecker@adacore.com> | 2014-08-14 15:57:00 -0700 |
---|---|---|
committer | Joel Brobecker <brobecker@adacore.com> | 2014-08-18 18:13:29 +0200 |
commit | 950c97d860f07274cad59b71c57704793e7f5a83 (patch) | |
tree | 3f81b5605cbf6490c7a0304a4c6f081033a3cdf2 /gdb/utils.c | |
parent | 3cdcd0ce16272ae8e8183699a341d081b6eb1b21 (diff) | |
download | binutils-950c97d860f07274cad59b71c57704793e7f5a83.zip binutils-950c97d860f07274cad59b71c57704793e7f5a83.tar.gz binutils-950c97d860f07274cad59b71c57704793e7f5a83.tar.bz2 |
[Ada] "ptype" of array where bound value uses DW_OP_push_object_address
Consider an Ada array type where the DWARF debugging info for
at least one of the bounds involves an expression containing
a DW_OP_push_object_address operation. Trying to "ptype" that
type currently yields:
(gdb) ptype foo.array_type
type = array (Location address is not set.
This patch improves ada-typeprint by adding handling of the situation
where an array range type has dynamic bounds. In that case, it prints
the array bounds using Ada's typical syntax for unbounded ranges "<>":
(gdb) ptype array_type
type = array (<>) of integer
gdb/ChangeLog:
* ada-typeprint.c (type_is_full_subrange_of_target_type):
Return 0 if TYPE is dynamic.
(print_range): Add handling of dynamic ranges.
Diffstat (limited to 'gdb/utils.c')
0 files changed, 0 insertions, 0 deletions