kfail gdb.python/py-evsignal.exp on RSP targets properly
authorPedro Alves <palves@redhat.com>
Fri, 13 Oct 2017 11:27:49 +0000 (12:27 +0100)
committerPedro Alves <palves@redhat.com>
Fri, 13 Oct 2017 11:29:49 +0000 (12:29 +0100)
Fixes, with --target_board=native-extended-gdbserver:

   Running ..../src/gdb/testsuite/gdb.python/py-evsignal.exp ...
   FAIL: gdb.python/py-evsignal.exp: signal Thread 3

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

* gdb.python/py-evsignal.exp: Check gdb_protocol instead of
is_remote.

gdb/testsuite/ChangeLog
gdb/testsuite/gdb.python/py-evsignal.exp

index 6296e10..4c01102 100644 (file)
@@ -1,5 +1,10 @@
 2017-10-13  Pedro Alves  <palves@redhat.com>
 
+       * gdb.python/py-evsignal.exp: Check gdb_protocol instead of
+       is_remote.
+
+2017-10-13  Pedro Alves  <palves@redhat.com>
+
        * gdb.threads/thread_events.exp: Check gdb_protocol instead of
        is_remote.
 
index 8a39f4e..4138b9c 100644 (file)
@@ -13,7 +13,8 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
 
-if {[is_remote target]} {
+if {[target_info gdb_protocol] == "remote"
+    || [target_info gdb_protocol] == "extended-remote"} {
     # RuntimeError: Could not find event thread
     kfail "python/12966" "Signal Thread 3"
     return -1