[pushed] Skip gdb.threads/thread_events.exp on RSP targets properly
Commit Message
Fixes, with --target_board=native-extended-gdbserver:
Running ..../src/gdb/testsuite/gdb.threads/thread_events.exp ...
FAIL: gdb.threads/thread_events.exp: continue to after_join_func with messages enabled (saw 0, expected 1)
gdb/testsuite/ChangeLog:
2017-10-13 Pedro Alves <palves@redhat.com>
* gdb.threads/thread_events.exp: Check gdb_protocol instead of
is_remote.
---
gdb/testsuite/ChangeLog | 5 +++++
gdb/testsuite/gdb.threads/thread_events.exp | 7 ++++---
2 files changed, 9 insertions(+), 3 deletions(-)
@@ -1,5 +1,10 @@
2017-10-13 Pedro Alves <palves@redhat.com>
+ * gdb.threads/thread_events.exp: Check gdb_protocol instead of
+ is_remote.
+
+2017-10-13 Pedro Alves <palves@redhat.com>
+
* gdb.base/corefile.exp (corefile_test_run): Skip if gdb_protocol
is set.
(corefile_test_attach): Likewise. Check can_spawn_for_attach
@@ -27,9 +27,10 @@ if ![istarget *-*-linux*] then {
return
}
-# When using gdbserver, even on Linux, we don't get notifications
-# about new threads. This is expected, so don't test for that.
-if [is_remote target] then {
+# When using the RSP, we don't get notifications about new threads.
+# This is expected, so don't test for that.
+if {[target_info gdb_protocol] == "remote"
+ || [target_info gdb_protocol] == "extended-remote"} {
return
}