aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTiezhu Yang <yangtiezhu@loongson.cn>2022-03-01 15:03:00 +0800
committerTiezhu Yang <yangtiezhu@loongson.cn>2022-03-01 15:21:11 +0800
commit863cd1c236deac344743156b58e28e79a7677e6f (patch)
treef4dde106db6d2e860ada66bb53ba2db160e54734
parentd3827c8d2de053f460ad90187593263fc273fe7f (diff)
downloadfsf-binutils-gdb-863cd1c236deac344743156b58e28e79a7677e6f.zip
fsf-binutils-gdb-863cd1c236deac344743156b58e28e79a7677e6f.tar.gz
fsf-binutils-gdb-863cd1c236deac344743156b58e28e79a7677e6f.tar.bz2
gdb: testsuite: print explicit test result in can_spawn_for_attach
In the current code, there is no test result when execute the following commands: $ make check-gdb TESTS="gdb.base/attach-pie-noexec.exp" RUNTESTFLAGS="--target_board=remote-gdbserver-on-localhost" $ make check-gdb TESTS="gdb.base/attach-pie-noexec.exp" RUNTESTFLAGS="--target_board=native-gdbserver" It is better to print explicit test result in can_spawn_for_attach. Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
-rw-r--r--gdb/testsuite/lib/gdb.exp2
1 files changed, 2 insertions, 0 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 2688a8e..8fafcc0 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5086,6 +5086,7 @@ proc can_spawn_for_attach { } {
# back the pid of the program. On remote boards, that would give
# us instead the PID of e.g., the ssh client, etc.
if [is_remote target] then {
+ unsupported "skip attach tests (target is remote)"
return 0
}
@@ -5093,6 +5094,7 @@ proc can_spawn_for_attach { } {
# stub-like, where GDB finds the program already started on
# initial connection.
if {[target_info exists use_gdb_stub]} {
+ unsupported "skip attach tests (target is stub)"
return 0
}