From: Tiezhu Yang <yangtiezhu@loongson.cn>
Date: Tue, 1 Mar 2022 07:03:00 +0000 (+0800)
Subject: gdb: testsuite: print explicit test result in can_spawn_for_attach
X-Git-Tag: gdb-12.1-release~206
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=863cd1c236deac344743156b58e28e79a7677e6f;p=thirdparty%2Fbinutils-gdb.git

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>
---

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 2688a8e0394..8fafcc03a18 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
     }