testsuite: Mark the kill in gdbserver_run as optional

This matches the kill in gdb_file_cmd, and ensures that the command is not
sent to the gdb.in file.

When gdb.in is used as a batch file, any kill commands run before the target
is started will cause gdb to stop processing commands.

gdb/testsuite/ChangeLog:

	* lib/gdbserver-support.exp (gdbserver_run): Mark kill as optional.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 5cfad2754e6473aada84549c720975f245bb0217..176b7f74bece01a3629fe117a9f99a5e68605997 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2019-05-21  Alan Hayward  <alan.hayward@arm.com>
+
+       * lib/gdbserver-support.exp (gdbserver_run): Mark kill as optional.
+
 2019-05-18  Andrew Burgess  <andrew.burgess@embecosm.com>
 
        PR gdb/18644

diff --git a/gdb/testsuite/lib/gdbserver-support.exp b/gdb/testsuite/lib/gdbserver-support.exp
index 2ccc717ef608265e1945fc4376febcfb6f302227..ade99c0ea16cb52f67fa079d573d6109c17d7c51 100644 (file)
--- a/gdb/testsuite/lib/gdbserver-support.exp
+++ b/gdb/testsuite/lib/gdbserver-support.exp
@@ -484,7 +484,7 @@ proc gdbserver_run { child_args } {
     # Kill anything running before we try to start gdbserver, in case
     # we are sharing a serial connection.
     global gdb_prompt
-    send_gdb "kill\n"
+    send_gdb "kill\n" optional
     gdb_expect 120 {
        -re "Kill the program being debugged. .y or n. $" {
            send_gdb "y\n"