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/NEWS | |
| 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/NEWS')
| -rw-r--r-- | gdb/NEWS | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -19,6 +19,11 @@ show source open to open and read source code files, which can be useful if the files are located over a slow network connection. +set varsize-limit +show varsize-limit + These are now deprecated aliases for "set max-value-size" and + "show max-value-size". + maint set internal-error backtrace on|off maint show internal-error backtrace maint set internal-warning backtrace on|off |