Created attachment 11720 [details] proposed fix to the GDB manual At least two Emacs developers were confused by GDB's documentation for reverse execution. One said he could never get it to work and recommended another debugger instead since it always worked for him. We tracked down the issue to a problem in GDB's documentation: it documents how to do reverse execution, but never mentions until a later section that you can't use reverse execution unless you first turn on process recording. Surely it's not intended that one must read the GDB documentation backwards in order to know how to do reverse execution.... Proposed patch attached.
Thanks for the patch. Patches aren't normally reviewed in bugzilla, but rather on the mailing list. See https://sourceware.org/gdb/wiki/ContributionChecklist
I just checked the GDB documentation and found the following paragraph on the page that introduces reverse debugging: On some platforms, gdb has built-in support for reverse execution, activated with the record or record btrace commands. See Chapter 7 [Process Record and Replay], page 101. Some remote targets, typically full system emulators, support reverse execution directly without requiring any special command. It is the 4th paragraph and comes before the explanation of commands. Is this issue fixed already, or would you still like improvements?