Skip a few tests on targets that can't use the "run" commmand.
authorPedro Alves <palves@redhat.com>
Thu, 12 Oct 2017 17:20:25 +0000 (18:20 +0100)
committerPedro Alves <palves@redhat.com>
Fri, 13 Oct 2017 17:11:31 +0000 (18:11 +0100)
commit300b6685f17cae131166eaf2fcafe10dab06466b
tree5ca5331347e01f842a7dd3bc15e2f42f9fde9809
parent50500caf810fcc6c05e3fd89bc37fe8f9e4adb07
Skip a few tests on targets that can't use the "run" commmand.

These tests want to use raw "run", so skip them on targets that can't
do that.

Also adds a small utility procedure that clearly conveys intent instead of
explicitly checking use_gdb_stub in the testcases.

This makes sure these testcases continue to be skipped with
--target_board=native-gdbserver once that board stops setting
is_remote.

gdb/testsuite/ChangeLog:
2017-10-13  Pedro Alves  <palves@redhat.com>

* lib/gdb.exp (target_can_use_run_cmd): New procedure.
* gdb.base/annota1.exp: Use it instead of is_remote.
* gdb.base/annota3.exp: Use it instead of is_remote.
* gdb.cp/annota2.exp: Use it instead of is_remote.
* gdb.cp/annota3.exp: Use it instead of is_remote.
* gdb.multi/bkpt-multi-exec.exp: Use it instead of is_remote.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/annota1.exp
gdb/testsuite/gdb.base/annota3.exp
gdb/testsuite/gdb.cp/annota2.exp
gdb/testsuite/gdb.cp/annota3.exp
gdb/testsuite/gdb.multi/bkpt-multi-exec.exp
gdb/testsuite/lib/gdb.exp