Fix is_remote check in gdb.base/remote.exp
authorPedro Alves <palves@redhat.com>
Fri, 13 Oct 2017 09:48:42 +0000 (10:48 +0100)
committerPedro Alves <palves@redhat.com>
Fri, 13 Oct 2017 10:20:37 +0000 (11:20 +0100)
commit23fb630af09f2601e7cb75233837399d67cfd017
tree1d661f78af81bb1a6f2cdc8fc90cc5fae93c9405
parentcc77b1dc33790bcb852c8c72e2efebaa3b505b01
Fix is_remote check in gdb.base/remote.exp

1. Otherwise, when the native-gdbserver board stops setting is_remote,
   this test would stop running there.

2. Makes the test run with --target_board=native-extended-gdbserver
   too.

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

* gdb.base/remote.exp: Check gdb_protocol instead of is_remote.
(top level): Add comment.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/remote.exp