From patchwork Tue May 21 09:08:01 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alan Hayward X-Patchwork-Id: 32779 Received: (qmail 68974 invoked by alias); 21 May 2019 09:08:15 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Delivered-To: mailing list gdb-patches@sourceware.org Received: (qmail 68958 invoked by uid 89); 21 May 2019 09:08:15 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-24.1 required=5.0 tests=AWL, BAYES_00, GIT_PATCH_0, GIT_PATCH_1, GIT_PATCH_2, GIT_PATCH_3, MIME_BASE64_BLANKS, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=Testsuite X-HELO: EUR03-DB5-obe.outbound.protection.outlook.com Received: from mail-eopbgr40087.outbound.protection.outlook.com (HELO EUR03-DB5-obe.outbound.protection.outlook.com) (40.107.4.87) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 21 May 2019 09:08:05 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Bu7m+XEmi8xsabctLjwg7vXcRRx+UMPZl313jTVqMWA=; b=srPjeUxV2Qq72Hiz0ofo3xu5uSq9/paRb7O8eSBeqTxT2hdFRibswPMtDdsAEhYdTAbUOZ3r5UhPwqS9iYWVXk3YhuTpGg0Oa6Zuk9X4sDVTRoO3Fwx4vxu78lxTDEDBB2WGqpwqtDnJmwH2jmK2GbBXsgPlgakQ0u5rEamMjUo= Received: from DB6PR0802MB2133.eurprd08.prod.outlook.com (10.172.227.22) by DB6PR0802MB2246.eurprd08.prod.outlook.com (10.172.228.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.18; Tue, 21 May 2019 09:08:02 +0000 Received: from DB6PR0802MB2133.eurprd08.prod.outlook.com ([fe80::8c26:bb4b:6c93:9d40]) by DB6PR0802MB2133.eurprd08.prod.outlook.com ([fe80::8c26:bb4b:6c93:9d40%2]) with mapi id 15.20.1900.020; Tue, 21 May 2019 09:08:01 +0000 From: Alan Hayward To: "gdb-patches@sourceware.org" CC: nd , Alan Hayward Subject: [PATCH] Document gdb.in/gdb.cmd files and debugredirect cli command Date: Tue, 21 May 2019 09:08:01 +0000 Message-ID: <20190521090758.62153-1-alan.hayward@arm.com> authentication-results: spf=none (sender IP is ) smtp.mailfrom=Alan.Hayward@arm.com; x-ms-oob-tlc-oobclassifiers: OLM:8882; received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 MIME-Version: 1.0 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-IsSubscribed: yes 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. [Wasn't sure if testsuite changes belonged in NEWS? If not I can drop that part] --- gdb/NEWS | 11 +++++++++++ gdb/doc/gdb.texinfo | 3 +++ gdb/testsuite/README | 21 +++++++++++++++++++++ 3 files changed, 35 insertions(+) -- 2.20.1 (Apple Git-117) diff --git a/gdb/NEWS b/gdb/NEWS index 1e92a2b52c..792548139e 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 diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 37e2f14ad0..bc21601606 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -1477,6 +1477,9 @@ you want @code{set logging on} to overwrite the logfile instead. @item set logging redirect [on|off] By default, @value{GDBN} output will go to both the terminal and the logfile. Set @code{redirect} if you want output to go only to the log file. +@item set logging debugredirect [on|off] +By default, @value{GDBN} debug output will go to both the terminal and the logfile. +Set @code{debugredirect} if you want debug output to go only to the log file. @kindex show logging @item show logging Show the current values of the logging settings. diff --git a/gdb/testsuite/README b/gdb/testsuite/README index b6487cf8c4..4795df1f75 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 *****************************