Re: GDB MI Reverse Commands added [2 of 3]

[Michael Snyder <msnyder@vmware.com>]

Eli Zaretskii wrote:
>> Date: Fri, 28 Aug 2009 10:35:13 -0700
>> From: Michael Snyder <msnyder@vmware.com>
>> CC: Greg Law <glaw@undo-software.com>, 
>>  "jakob@virtutech.com" <jakob@virtutech.com>,
>>  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>>
>> I think we should mention that "running off the end of the log" is
>> one way in which a reverse continue may terminate, because in fact
>> that is something that may happen in all of the current implementations.
> 
> Please suggest a wording, and if it's clear, I won't mind.

How about this?  (please add markups)

Resumes the execution of the inferior program, which will continue
to execute until it reaches a debugger stop event.  If the 
@samp{--reverse} option is specified, execution resumes in reverse until 
it reaches a stop event.  Stop events may include
  * breakpoints or watchpoints
  * signals or exceptions)
  * the end of the process (or its beginning if --reverse)
  * the end (beginning) of a replay log if one is being used.