testsuite: Add replay logging to GDBSERVER_DEBUG
authorAlan Hayward <alan.hayward@arm.com>
Tue, 30 Apr 2019 15:00:29 +0000 (16:00 +0100)
committerAlan Hayward <alan.hayward@arm.com>
Fri, 17 May 2019 15:44:17 +0000 (16:44 +0100)
commitb420b89e4b321ff31f2e76cac499b908f042069b
treec96ab0dac761d97a468a7efdf4d76d1484fe26df
parent408e9b8b9ebeb854baea9aac52fa8df4d41eb53d
testsuite: Add replay logging to GDBSERVER_DEBUG

Add "replay" to the list of GDBSERVER_DEBUG options.  This will
cause a gdbserver.replay file to be written to the test output
directory.

At the same time switch this to a comma separated list in order
to easily handle all possible options.

The replay log is created by GDB, but has been added to
GDBSERVER_DEBUG as it is only required for gdbserver tests. To
enable it, the gdb_debug_init is overridden to allow the additional
checking, before calling the original function.

gdb/testsuite/ChangeLog:

        * README (Testsuite Parameters): Add replay logging to
        GDBSERVER_DEBUG.
        (gdbserver,debug): Refer to GDBSERVER_DEBUG.
        * lib/gdbserver-support.exp (gdbserver_start): Treat gdbserverdebug
        as a comma separated list.
        (gdb_debug_init): Override procedure.
gdb/testsuite/ChangeLog
gdb/testsuite/README
gdb/testsuite/lib/gdbserver-support.exp