Skip gdb.threads/thread_events.exp on RSP targets properly
authorPedro Alves <palves@redhat.com>
Fri, 13 Oct 2017 11:18:50 +0000 (12:18 +0100)
committerPedro Alves <palves@redhat.com>
Fri, 13 Oct 2017 11:23:32 +0000 (12:23 +0100)
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
gdb/testsuite/gdb.threads/thread_events.exp

index 3532ed3ed07198ae7aa1aa4a2451838a95794235..6296e10cfd4042c765cc6e28bdcb0fdd33552945 100644 (file)
@@ -1,3 +1,8 @@
+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
index d8d19c852108ac2a85b523af679159042c6ba09f..7ccef55286942c5f17be107fb55384c0603d647b 100644 (file)
@@ -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
 }