testsuite: Create .cmd files for gdb and gdbserver
authorAlan Hayward <alan.hayward@arm.com>
Fri, 17 May 2019 15:38:02 +0000 (16:38 +0100)
committerAlan Hayward <alan.hayward@arm.com>
Fri, 17 May 2019 15:38:02 +0000 (16:38 +0100)
commit408e9b8b9ebeb854baea9aac52fa8df4d41eb53d
treee36e2bb0fd1758359e041ffb1ca5f34dfa64c348
parentf9e2e39d23495844d998f54a0fccb9d6be7edb0e
testsuite: Create .cmd files for gdb and gdbserver

When spawning gdb or gdbserver create a .cmd file in the test output
directory containing the full command line, ensuring the current gdb
instance is appended to the files so that they can be quickly matched
to the corresponding gdb.in file.

gdb/testsuite/ChangeLog:

* lib/gdb.exp (default_gdb_spawn): Call gdb_write_cmd_file.
(gdb_write_cmd_file): New procedure.
* lib/gdbserver-support.exp (gdbserver_start): Call
gdbserver_write_cmd_file.
(gdbserver_write_cmd_file): New proedure.
gdb/testsuite/ChangeLog
gdb/testsuite/lib/gdb.exp
gdb/testsuite/lib/gdbserver-support.exp