public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "trass3r at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/29260] New: Stopped event should contain reason for 'No more reverse-execution history'
Date: Fri, 17 Jun 2022 17:35:56 +0000 [thread overview]
Message-ID: <bug-29260-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29260
Bug ID: 29260
Summary: Stopped event should contain reason for 'No more
reverse-execution history'
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: record
Assignee: unassigned at sourceware dot org
Reporter: trass3r at gmail dot com
Target Milestone: ---
When stepping past the reverse execution history buffer bounds
gdb prints 'No more reverse-execution history' to the output but does not give
a reason in the MI stopped event, leading to a bad UX.
https://github.com/microsoft/MIEngine/pull/1037#issuecomment-750299377
1: (62155) <-1057-exec-next --reverse
1: (62156) ->1057^running
1: (62156) ->*running,thread-id="1"
1: (62156) ->(gdb)
1: (62163) ->~"\nNo more reverse-execution history.\n"
1: (62164) ->~"main (argc=1, argv=0x7fffffffdb78) at ../test.cpp:25\n"
1: (62164) ->~"25\t\tstd::u16string s = u\"test\";\n"
1: (62164)
->*stopped,frame={addr="0x000055555555734b",func="main",args=[{name="argc",value="1"},{name="argv",value="0x7fffffffdb78"}],file="../test.cpp",fullname="/tmp/test.cpp",line="25",arch="i386:x86-64"},thread-id="1",stopped-threads="all",core="2"
Test case:
https://github.com/microsoft/MIEngine/pull/1037#issuecomment-1158743492
int main()
{
int i = 0;
++i;
++i;
return i;
}
$ gdb --batch -ex 'b main' -ex r -ex n -ex 'p i' -ex 'record full' -ex n -ex 'p
i' -ex n -ex 'p i' -ex n -ex 'p i' -ex 'reverse-next' -ex 'p i' -ex
'reverse-next' -ex 'p i' -ex 'reverse-next' -ex 'p i' test
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-17 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 17:35 trass3r at gmail dot com [this message]
2022-06-17 20:58 ` [Bug record/29260] " trass3r at gmail dot com
2022-06-18 16:20 ` tromey at sourceware dot org
2022-06-18 17:08 ` trass3r at gmail dot com
2022-06-18 17:09 ` trass3r at gmail dot com
2023-01-18 13:49 ` blarsen at redhat dot com
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=bug-29260-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).