Re: reverse execution part of the manual is written backwards

[Paul Eggert <eggert@cs.ucla.edu>]

[-- Attachment #1: Type: text/plain, Size: 160 bytes --]

Pedro Alves wrote:
> This is not correct.  "record" is one way to support reverse execution,
> but there are others.

OK, how about the attached patch instead?

[-- Attachment #2: gdb-diff.txt --]
[-- Type: text/plain, Size: 867 bytes --]

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index f410d026b8..6410e9cc7b 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -6697,8 +6697,13 @@ assumes that the memory and registers that the target reports are in a
 consistant state, but @value{GDBN} accepts whatever it is given.
 }.
 
-If you are debugging in a target environment that supports
-reverse execution, @value{GDBN} provides the following commands.
+Not every target environment supports reverse execution, and some
+targets require that you first use the @code{record} or @code{record
+btrace} command, so that instructions executed by the program are
+saved for reverse execution later.  @xref{Process Record and Replay}.
+
+@value{GDBN} provides the following commands to examine the process
+record and execute the program in reverse.
 
 @table @code
 @kindex reverse-continue