From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Cc: Bruno Larsen <blarsen@redhat.com>
Subject: [PATCH] gdb/mi: add no-history stop reason
Date: Mon, 2 Jan 2023 16:56:45 +0100 [thread overview]
Message-ID: <20230102155645.66733-1-blarsen@redhat.com> (raw)
When executing in reverse and runs out of recorded history, GDB prints
a warning to the user, but does not add a reason in the stopped record,
for example:
*stopped,frame={addr="0x000000000040113e",func="main",args=[],file="/home/blarsen/Documents/fsf_build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.reverse/solib-reverse.c",fullname="/home/blarsen/Documents/binutils-gdb/gdb/testsuite/gdb.reverse/solib-reverse.c",line="27",arch="i386:x86-64"},thread-id="1",stopped-threads="all",core="1"
This problem was reported as record/29260.
This commit adds the reason no-history to the record, making it easier
for interfaces using the mi interpreter to report the result.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29260
---
gdb/NEWS | 5 +++++
gdb/doc/gdb.texinfo | 2 ++
gdb/infrun.c | 5 ++++-
3 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index e61f06081de..3673bed8f46 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -5,6 +5,11 @@
* MI version 1 has been removed.
+* MI changes
+
+** mi now reports 'no_history' as a stop reason when hitting the end of the
+ reverse execution history.
+
*** Changes in GDB 13
* MI version 1 is deprecated, and will be removed in GDB 14.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index a72b2b9eb26..8982151a7e3 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -30851,6 +30851,8 @@ The inferior returned from a system call. This is reported when
@item exec
The inferior called @code{exec}. This is reported when @code{catch exec}
(@pxref{Set Catchpoints}) has been used.
+@item no-history
+There isn't enough history recorded to continue reverse execution.
@end table
The @var{id} field identifies the global thread ID of the thread
diff --git a/gdb/infrun.c b/gdb/infrun.c
index d5f97e33625..601d1a54701 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -8406,7 +8406,10 @@ print_signal_received_reason (struct ui_out *uiout, enum gdb_signal siggnal)
void
print_no_history_reason (struct ui_out *uiout)
{
- uiout->text ("\nNo more reverse-execution history.\n");
+ if (uiout->is_mi_like_p ())
+ uiout->field_string ("reason", "no-history");
+ else
+ uiout->text ("\nNo more reverse-execution history.\n");
}
/* Print current location without a level number, if we have changed
--
2.39.0
next reply other threads:[~2023-01-02 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 15:56 Bruno Larsen [this message]
2023-01-03 12:04 ` Andrew Burgess
2023-01-04 14:40 ` Bruno Larsen
2023-01-10 15:36 ` Pedro Alves
2023-01-10 15:39 ` Bruno 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=20230102155645.66733-1-blarsen@redhat.com \
--to=blarsen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).