Really make the native-stdio-gdbserver board non-remote

I've noticed now that due to a last-minute change, commit 739b3f1d8ff7
("Make native gdbserver boards no longer be "remote" (in DejaGnu
terms)") managed to miss loading "local-board" in the
native-stdio-gdbserver board...

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

	* boards/native-stdio-gdbserver.exp: Load "local-board".

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 13265ba..ddfce31 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,5 +1,9 @@
 2017-10-17  Pedro Alves  <palves@redhat.com>
 
+       * boards/native-stdio-gdbserver.exp: Load "local-board".
+
+2017-10-17  Pedro Alves  <palves@redhat.com>
+
        * gdb.base/quit-live.c: New file.
        * gdb.base/quit-live.exp: New file.
 

diff --git a/gdb/testsuite/boards/native-stdio-gdbserver.exp b/gdb/testsuite/boards/native-stdio-gdbserver.exp
index f8e7468..23c22fe 100644 (file)
--- a/gdb/testsuite/boards/native-stdio-gdbserver.exp
+++ b/gdb/testsuite/boards/native-stdio-gdbserver.exp
@@ -21,6 +21,7 @@
 # bash$ make check RUNTESTFLAGS="--target_board=native-stdio-gdbserver"
 
 load_board_description "stdio-gdbserver-base"
+load_board_description "local-board"
 
 proc get_target_remote_pipe_cmd {} {
     global last_loaded_file