diff options
| author | Tom Tromey <tromey@adacore.com> | 2021-09-13 12:53:05 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2021-10-05 12:35:24 -0600 |
| commit | acbf4a58ef324e506cad9cc867a67164d2ca19d4 (patch) | |
| tree | 01ef3482d2859a81ca7a94e09c7ff190838fcde9 /gdb/ada-valprint.c | |
| parent | 3e44c3049fc23f5ba894b346b7defdfba66b076e (diff) | |
| download | gdb-acbf4a58ef324e506cad9cc867a67164d2ca19d4.zip gdb-acbf4a58ef324e506cad9cc867a67164d2ca19d4.tar.gz gdb-acbf4a58ef324e506cad9cc867a67164d2ca19d4.tar.bz2 | |
Remove 'varsize-limit'
This makes the Ada-specific "varsize-limit" a synonym for
"max-value-size", and removes the Ada-specific checks of the limit.
I am not certain of the history here, but it seems to me that this
code is fully obsolete now. And, removing this makes it possible to
index large Ada arrays without triggering an error. A new test case
is included to demonstrate this.
Diffstat (limited to 'gdb/ada-valprint.c')
| -rw-r--r-- | gdb/ada-valprint.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/gdb/ada-valprint.c b/gdb/ada-valprint.c index 979487f..e725cd3 100644 --- a/gdb/ada-valprint.c +++ b/gdb/ada-valprint.c @@ -970,12 +970,6 @@ ada_val_print_ref (struct type *type, const gdb_byte *valaddr, if (ada_is_tagged_type (value_type (deref_val), 1)) deref_val = ada_tag_value_at_base_address (deref_val); - /* Make sure that the object does not have an unreasonable size - before trying to print it. This can happen for instance with - references to dynamic objects whose contents is uninitialized - (Eg: an array whose bounds are not set yet). */ - ada_ensure_varsize_limit (value_type (deref_val)); - if (value_lazy (deref_val)) value_fetch_lazy (deref_val); |