From b706061469811a16ff2fb8d42f6e98a22e454212 Mon Sep 17 00:00:00 2001 From: Alan Hayward Date: Wed, 22 May 2019 13:40:20 +0100 Subject: 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. --- gdb/NEWS | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'gdb/NEWS') diff --git a/gdb/NEWS b/gdb/NEWS index 1e92a2b..7925481 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -46,6 +46,10 @@ show print max-depth The default max-depth is 20, but this can be set to unlimited to get the old behavior back. +set logging debugredirect [on|off] + By default, GDB debug output will go to both the terminal and the logfile. + Set if you want debug output to go only to the log file. + * New MI commands -complete @@ -53,6 +57,13 @@ show print max-depth were to be given as a command itself. This is intended for use by MI frontends in cases when separate CLI and MI channels cannot be used. +* Testsuite + + The testsuite now creates the files gdb.cmd (containing the arguments + used to launch GDB) and gdb.in (containing all the commands sent to + GDB) in the output directory for each test script. Multiple invocations + are appended with .1, .2, .3 etc. + *** Changes in GDB 8.3 * GDB and GDBserver now support access to additional registers on -- cgit v1.1