From: Guinevere Larsen <guinevere@redhat.com>
To: gdb-patches@sourceware.org
Cc: Guinevere Larsen <guinevere@redhat.com>
Subject: [PATCH] gdb/reverse: update error message for "reverse-" commands
Date: Thu, 23 Oct 2025 15:33:42 -0300 [thread overview]
Message-ID: <20251023183342.219421-1-guinevere@redhat.com> (raw)
Before this change, when a user tried to use a command that executes the
inferior in reverse, they would get the following error message:
Target multi-thread does not support this command.
As an end-user with no knowledge of the internals of GDB would have as a
best guess, that reverse execution as a whole would not be supported in
their system (verified by asking a couple new users).
This commit changes the message to avoid the internal terminology, and
to add a hint that the user may need to create a recording somehow to be
able to execute in reverse.
---
gdb/reverse.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gdb/reverse.c b/gdb/reverse.c
index bda23ed2199..0d67afad45e 100644
--- a/gdb/reverse.c
+++ b/gdb/reverse.c
@@ -44,7 +44,8 @@ exec_reverse_once (const char *cmd, const char *args, int from_tty)
cmd);
if (!target_can_execute_reverse ())
- error (_("Target %s does not support this command."), target_shortname ());
+ error (_("Reverse execution is not currently supported.\n"
+ "You may need to record the execution first."));
std::string reverse_command = string_printf ("%s %s", cmd, args ? args : "");
scoped_restore restore_exec_dir
base-commit: 8eeb52e3c7701f03711d51a2209c39d85d109500
--
2.51.0
next reply other threads:[~2025-10-23 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 18:33 Guinevere Larsen [this message]
2025-10-24 18:42 ` Tom Tromey
2025-10-24 18:44 ` Guinevere Larsen
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=20251023183342.219421-1-guinevere@redhat.com \
--to=guinevere@redhat.com \
--cc=gdb-patches@sourceware.org \
/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