[gdb/testsuite] Use proc readnow in two test-cases

Use "require !readnow" in two test-cases, instead of the written-out variant.

Tested on x86_64-linux, with target boards unix and readnow.
This commit is contained in:
Tom de Vries 2023-07-22 11:00:25 +02:00
parent 6fbe38ce11
commit 09075d5d4a
2 changed files with 8 additions and 14 deletions

View file

@ -17,6 +17,10 @@
# syscall is active. But some active syscalls keep PC pointing to the SVC
# instruction itself.
# See if we have target board readnow.exp or similar. We're using
# --readnever, which is not allowed in combination with --readnow.
require !readnow
standard_testfile
if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile} \
@ -24,13 +28,6 @@ if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile} \
return
}
# See if we have target board readnow.exp or similar.
if { [lsearch -exact $GDBFLAGS -readnow] != -1 \
|| [lsearch -exact $GDBFLAGS --readnow] != -1 } {
untested "--readnever not allowed in combination with --readnow"
return -1
}
save_vars { GDBFLAGS } {
append GDBFLAGS " --readnever"
if { [clean_restart ${binfile}] == -1 } {

View file

@ -13,6 +13,10 @@
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# See if we have target board readnow.exp or similar. We're using
# --readnever, which is not allowed in combination with --readnow.
require !readnow
standard_testfile .c
if { [build_executable "failed to build" $testfile $srcfile { debug }] == -1 } {
@ -20,13 +24,6 @@ if { [build_executable "failed to build" $testfile $srcfile { debug }] == -1 } {
return -1
}
# See if we have target board readnow.exp or similar.
if { [lsearch -exact $GDBFLAGS -readnow] != -1 \
|| [lsearch -exact $GDBFLAGS --readnow] != -1 } {
untested "--readnever not allowed in combination with --readnow"
return -1
}
save_vars { GDBFLAGS } {
append GDBFLAGS " --readnever"
if { [clean_restart ${binfile}] == -1 } {