gdb/mi: add no-history stop reason
authorBruno Larsen <blarsen@redhat.com>
Mon, 2 Jan 2023 13:35:50 +0000 (14:35 +0100)
committerBruno Larsen <blarsen@redhat.com>
Fri, 6 Jan 2023 09:51:50 +0000 (10:51 +0100)
commit37f54063ed0daaffbd52f69efbdb4c8e0a9c9cca
tree0cf886601fb04de161f8417f6363cf7e561728e4
parent695e9773786d79f191e9487a88d3b39a57d9c7e7
gdb/mi: add no-history stop reason

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.  It also
changes the test gdb.mi/mi-reverse.exp to test that the reason shows up
correctly.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29260
gdb/NEWS
gdb/doc/gdb.texinfo
gdb/infrun.c
gdb/mi/mi-common.c
gdb/mi/mi-common.h
gdb/testsuite/gdb.mi/mi-reverse.exp