OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

testsuite: Mark the kill in gdbserver_run as optional

Browse Source 
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.
This commit is contained in:
Alan Hayward 2019-05-21 10:11:51 +01:00
parent e2d1595531
commit ce3ebcaae3
2 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/testsuite/ChangeLog
View File

@ -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

2
gdb/testsuite/lib/gdbserver-support.exp
View File

@ -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"