diff options
| author | Alan Hayward <alan.hayward@arm.com> | 2019-05-22 13:40:20 +0100 |
|---|---|---|
| committer | Alan Hayward <alan.hayward@arm.com> | 2019-05-22 13:40:20 +0100 |
| commit | b706061469811a16ff2fb8d42f6e98a22e454212 (patch) | |
| tree | b2888b7e8fb0a25c5ec6475200c5951237a00ffe /gdb/testsuite/README | |
| parent | 0a5954bd5f96dd665cb733b9ab6f2ca67bb4632d (diff) | |
| download | gdb-b706061469811a16ff2fb8d42f6e98a22e454212.zip gdb-b706061469811a16ff2fb8d42f6e98a22e454212.tar.gz gdb-b706061469811a16ff2fb8d42f6e98a22e454212.tar.bz2 | |
Document gdb.in/gdb.cmd files and debugredirect cli command
Add missing documentation for the debugredirect setting.
Add description and uses of gdb.in/gdb.cmd to the testsuite README.
Mention this in the NEWS file.
gdb/ChangeLog:
* NEWS: Add debugredirect and testsuite sections.
gdb/doc/ChangeLog:
* gdb.texinfo (Shell Commands): Add debugredirect.
gdb/testsuite/ChangeLog:
* README (Re-running Tests Outside The Testsuite): New section.
Diffstat (limited to 'gdb/testsuite/README')
| -rw-r--r-- | gdb/testsuite/README | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/gdb/testsuite/README b/gdb/testsuite/README index b6487cf..4795df1 100644 --- a/gdb/testsuite/README +++ b/gdb/testsuite/README @@ -95,6 +95,27 @@ example: The script will output its analysis report to the standard output. +Re-running Tests Outside The Testsuite +************************************** + +When running a test, the arguments used to run GDB are saved to gdb.cmd and +all commands sent to GDB are saved to gdb.in. As well as being a reference +of the commands run, they can be used to manually re-run a test by using +the gdb.in file as a batch file to a GDB launched with the arguments in the +gdb.cmd file, for example: + $(cat outputs/gdb.base/store/gdb.cmd) -x outputs/gdb.base/store/gdb.in + +Tests that run GDB multiple times will append .1, .2, .3 etc to the end +of each .cmd and .in file. + +When gdbserver is launched as part of a test, a gdbserver.cmd will be created. +To re-run these tests, run the contents of gdbserver.cmd in a separate +terminal before running gdb, for example: + $(cat outputs/gdb.base/store/gdbserver.cmd) +Alternatively, if the test is run with GDBSERVER_DEBUG="replay", then this +will create a gdbserver.replay file which can be used with the gdbreplay tool, +instead of launching gdbserver. + Running the Performance Tests ***************************** |