issues when stopping the inferior during replay

rr replay
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
0x00007f9c74914080 in _start () from /lib64/ld-linux-x86-64.so.2
Missing separate debuginfos, use: yum debuginfo-install glibc-2.28-127.el8.x86_64
(rr) c
Continuing.
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
^Cwarning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
Reply contains invalid hex digit 84
(rr) start
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Temporary breakpoint 1 at 0x401795: file cobcrun.c, line 377.
Starting program: /opt/gnucobol/gnucobol-3.1.2/bin/cobcrun
Malformed response to offset query, 1
Remote 'g' packet reply is too long (expected 560 bytes, got 816 bytes): 00000000000000000000000000000000ffffffffffffffff000000000000000000000000000000000000000000000000000000000000000090ed63a7fc7f000000000000000000000000000000000000000000000000000046020000000000000000000000000000000000000000000000000000000000000000000000000000804091749c7f000046020000330000002b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f0300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f00003b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
(rr)

The error message after [CTRL]+[C] seems to be specific on the exact place where that happened but in a row of three always returned the invalid hex digit 84:

^Cwarning: Probes-based dynamic linker interface failed.
Reverting to original interface.

Reply contains invalid hex digit 84

The message after the re- start was always the same in those tests.

Happened on Linux testvm 4.18.0-80.el8.x86_64 #1 SMP Tue Jun 4 09:19:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux, both with current master and 5.4.0 release both with the system-GDB and with GNU gdb (GDB) 9.2.

No source files, tests, or entry points are named. Start by reproducing rr replay, interrupting the inferior with Ctrl-C, and running start again on the reported Linux and GDB versions; done means the invalid hex, malformed response, and oversized remote-register packet errors no longer occur.