From: Markus Metzger via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] gdb, record: rephrase the 'not recording' error message
Date: Thu, 17 Dec 2020 16:12:08 +0100 [thread overview]
Message-ID: <20201217151212.1179058-1-markus.t.metzger@intel.com> (raw)
When trying to use one of the record commands without having enabled
recording first, GDB gives the error message:
(gdb) record function-call-history
No record target is currently active.
Use one of the "target record-<TAB><TAB>" commands first.
In the record help, however, we say:
(gdb) help record
record, rec
Start recording.
List of record subcommands:
record btrace, record b -- Start branch trace recording.
record delete, record del, record d -- Delete the rest of execution log and start recording it anew.
record full -- Start full execution recording.
record function-call-history -- Prints the execution history at function granularity.
record goto -- Restore the program to its state at instruction number N.
record instruction-history -- Print disassembled instructions stored in the execution log.
record save -- Save the execution log to a file.
record stop, record s -- Stop the record/replay target.
Change the above error message to
(gdb) record function-call-history
No recording is currently active.
Use the "record full" or "record btrace" command first.
to align with the help text.
gdb/ChangeLog:
2020-12-03 Markus Metzger <markus.t.metzger@intel.com>
* record.c (require_record_target): Rephrase error message.
(info_record_command): Likewise.
gdb/testsuite/ChangeLog:
2020-12-03 Markus Metzger <markus.t.metzger@intel.com>
* gdb.btrace/enable.exp: Update error message.
* gdb.btrace/multi-inferior.exp: Likewise.
* gdb.btrace/reconnect.exp: Likewise.
* gdb.python/py-record-btrace.exp: Likewise.
* gdb.python/py-record-full.exp: Likewise.
---
gdb/record.c | 6 +++---
gdb/testsuite/gdb.btrace/enable.exp | 10 +++++-----
gdb/testsuite/gdb.btrace/multi-inferior.exp | 4 ++--
gdb/testsuite/gdb.btrace/reconnect.exp | 2 +-
gdb/testsuite/gdb.python/py-record-btrace.exp | 2 +-
gdb/testsuite/gdb.python/py-record-full.exp | 2 +-
6 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/gdb/record.c b/gdb/record.c
index f9141192779..204bda0a424 100644
--- a/gdb/record.c
+++ b/gdb/record.c
@@ -74,8 +74,8 @@ require_record_target (void)
t = find_record_target ();
if (t == NULL)
- error (_("No record target is currently active.\n"
- "Use one of the \"target record-<TAB><TAB>\" commands first."));
+ error (_("No recording is currently active.\n"
+ "Use the \"record full\" or \"record btrace\" command first."));
return t;
}
@@ -325,7 +325,7 @@ info_record_command (const char *args, int from_tty)
t = find_record_target ();
if (t == NULL)
{
- printf_filtered (_("No record target is currently active.\n"));
+ printf_filtered (_("No recording is currently active.\n"));
return;
}
diff --git a/gdb/testsuite/gdb.btrace/enable.exp b/gdb/testsuite/gdb.btrace/enable.exp
index a968d410384..8ce1dab076f 100644
--- a/gdb/testsuite/gdb.btrace/enable.exp
+++ b/gdb/testsuite/gdb.btrace/enable.exp
@@ -27,15 +27,15 @@ gdb_exit
gdb_start
# record cannot be stopped, if it was never active
-gdb_test "record stop" "No record target is currently active\\..*" "record stop without target"
+gdb_test "record stop" "No recording is currently active\\..*" "record stop without target"
# btrace cannot be enabled without a running inferior
gdb_test "record btrace" "The program is not being run\\." "record btrace without running program"
# no function and no instruction history without btrace enabled
-gdb_test "record function-call-history" "No record target is currently active\\..*" "record function-call-history without target"
-gdb_test "record instruction-history" "No record target is currently active\\..*" "record instruction-history without target"
-gdb_test "info record" "No record target is currently active\\." "info record without target"
+gdb_test "record function-call-history" "No recording is currently active\\..*" "record function-call-history without target"
+gdb_test "record instruction-history" "No recording is currently active\\..*" "record instruction-history without target"
+gdb_test "info record" "No recording is currently active\\." "info record without target"
standard_testfile
if [prepare_for_testing "failed to prepare" $testfile {} {debug}] {
@@ -65,7 +65,7 @@ Recorded 0 instructions in 0 functions \\\(0 gaps\\\) for thread 1.*\\." "info r
# stop btrace record
gdb_test "record stop" "Process record is stopped and all execution logs are deleted\\."
-gdb_test "record stop" "No record target is currently active\\..*" "record stop the second time"
+gdb_test "record stop" "No recording is currently active\\..*" "record stop the second time"
# enable btrace again
gdb_test_no_output "record btrace" "record btrace re-enable"
diff --git a/gdb/testsuite/gdb.btrace/multi-inferior.exp b/gdb/testsuite/gdb.btrace/multi-inferior.exp
index fdf889f5ed8..23bc852c565 100644
--- a/gdb/testsuite/gdb.btrace/multi-inferior.exp
+++ b/gdb/testsuite/gdb.btrace/multi-inferior.exp
@@ -55,7 +55,7 @@ with_test_prefix "inferior 2" {
with_test_prefix "inferior 1" {
gdb_test "inferior 1" "Switching to inferior 1.*"
- gdb_test "info record" "No record target is currently active\\."
+ gdb_test "info record" "No recording is currently active\\."
gdb_test_no_output "record btrace" "record btrace"
}
@@ -69,6 +69,6 @@ with_test_prefix "inferior 3" {
return -1
}
- gdb_test "info record" "No record target is currently active\\."
+ gdb_test "info record" "No recording is currently active\\."
gdb_test_no_output "record btrace" "record btrace"
}
diff --git a/gdb/testsuite/gdb.btrace/reconnect.exp b/gdb/testsuite/gdb.btrace/reconnect.exp
index 26d04c38a9e..baec86f8aa3 100644
--- a/gdb/testsuite/gdb.btrace/reconnect.exp
+++ b/gdb/testsuite/gdb.btrace/reconnect.exp
@@ -81,5 +81,5 @@ with_test_prefix "second" {
# Test that recording is now off.
with_test_prefix "third" {
- gdb_test "info record" "No record target is currently active."
+ gdb_test "info record" "No recording is currently active."
}
diff --git a/gdb/testsuite/gdb.python/py-record-btrace.exp b/gdb/testsuite/gdb.python/py-record-btrace.exp
index bdfb2e3b125..3a84cbe7ac4 100644
--- a/gdb/testsuite/gdb.python/py-record-btrace.exp
+++ b/gdb/testsuite/gdb.python/py-record-btrace.exp
@@ -47,7 +47,7 @@ with_test_prefix "no or double record" {
gdb_test "python gdb.start_recording(\"btrace\")" ".*gdb\.error: The process is already being recorded\..*"
gdb_test_no_output "python gdb.stop_recording()" "first"
- gdb_test "python gdb.stop_recording()" ".*gdb\.error: No record target is currently active\..*" "second"
+ gdb_test "python gdb.stop_recording()" ".*gdb\.error: No recording is currently active\..*" "second"
}
with_test_prefix "preopened record btrace" {
diff --git a/gdb/testsuite/gdb.python/py-record-full.exp b/gdb/testsuite/gdb.python/py-record-full.exp
index c823bc2c74c..a1f24a3634f 100644
--- a/gdb/testsuite/gdb.python/py-record-full.exp
+++ b/gdb/testsuite/gdb.python/py-record-full.exp
@@ -47,7 +47,7 @@ with_test_prefix "no or double record" {
gdb_test "python gdb.start_recording(\"full\")" ".*gdb\.error: The process is already being recorded\..*"
gdb_test_no_output "python gdb.stop_recording()" "first"
- gdb_test "python gdb.stop_recording()" ".*gdb\.error: No record target is currently active\..*" "second"
+ gdb_test "python gdb.stop_recording()" ".*gdb\.error: No recording is currently active\..*" "second"
}
with_test_prefix "preopened record full" {
--
2.26.2
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2020-12-17 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:12 Markus Metzger via Gdb-patches [this message]
2020-12-17 15:12 ` [PATCH 1/4] testsuite, gdb.btrace: make test names unique Markus Metzger via Gdb-patches
2020-12-18 19:34 ` Simon Marchi via Gdb-patches
2020-12-21 7:26 ` Metzger, Markus T via Gdb-patches
2020-12-17 15:12 ` [PATCH 2/4] testsuite, gdb.python: make py-record-*.exp " Markus Metzger via Gdb-patches
2020-12-18 19:35 ` Simon Marchi via Gdb-patches
2020-12-17 15:12 ` [PATCH 3/4] testsuite, gdb.btrace: skip multi-inferior.exp on gdbserver targets Markus Metzger via Gdb-patches
2020-12-18 19:49 ` Simon Marchi via Gdb-patches
2020-12-21 7:27 ` Metzger, Markus T via Gdb-patches
2020-12-21 13:50 ` Simon Marchi via Gdb-patches
2020-12-17 15:12 ` [PATCH 4/4] testsuite, gdb.btrace: fix 32-bit PIE false positives Markus Metzger via Gdb-patches
2020-12-18 20:01 ` Simon Marchi via Gdb-patches
2020-12-21 7:27 ` Metzger, Markus T via Gdb-patches
2020-12-18 19:18 ` [PATCH] gdb, record: rephrase the 'not recording' error message Simon Marchi via Gdb-patches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201217151212.1179058-1-markus.t.metzger@intel.com \
--to=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox