binutils-gdb/gdb/testsuite/gdb.ada/varsize_limit.exp
Tom Tromey acbf4a58ef 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.
2021-10-05 12:35:24 -06:00

44 lines
1.4 KiB
Plaintext

# Copyright 2018-2021 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
load_lib "ada.exp"
if { [skip_ada_tests] } { return -1 }
standard_ada_testfile vsizelim
if {[gdb_compile_ada "${srcfile}" "${binfile}" executable [list debug ]] != "" } {
return -1
}
clean_restart ${testfile}
set bp_location [gdb_get_line_number "STOP" ${testdir}/vsizelim.adb]
if ![runto "vsizelim.adb:$bp_location" ] then {
perror "Couldn't run ${testfile}"
return
}
gdb_test "set varsize-limit 16" \
"Warning: command 'set varsize-limit' is deprecated.\r\nUse 'set max-value-size'."
gdb_test "print small" " = \"1234567890\""
gdb_test "print larger" "more than max-value-size.*"
gdb_test "print name.all" "more than max-value-size.*"
gdb_test "print ba.data(5)" " = 5" "print array element"