[PUSHED/OBV] testsuite: Mark the kill in gdbserver_run as optional
Commit Message
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.
---
gdb/testsuite/ChangeLog | 4 ++++
gdb/testsuite/lib/gdbserver-support.exp | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
--
2.20.1 (Apple Git-117)
@@ -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
@@ -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"