Re: [RFA] Reverse debugging, part 1/3: target interface

[Michael Snyder <msnyder@redhat.com>]

Daniel Jacobowitz wrote:
> On Tue, Apr 18, 2006 at 08:58:36AM -0400, Daniel Jacobowitz wrote:
> 
>>On Mon, Apr 17, 2006 at 04:37:43PM -0700, Michael Snyder wrote:
>>
>>>Two week ping...  there having been no objections to this patch,
>>>shall I check it in?
>>
>>For something this major, I think we should make sure someone else at
>>least looks over it first.  I haven't had time, and I was hoping that
>>someone else would take the time; but if no one does, I will
>>definitely get to it soon.
> 
> 
> Oh, I see one thing in a first look: you are adding to the remote
> protocol without adding documentation for the new packets or error
> codes.  Please document them!

Good point.  If anyone wants to modify them, now's the time.

How's this, at least for a start?

@@ -22554,6 +22660,16 @@
  Don't use this packet.  Use the @samp{Z} and @samp{z} packets instead
  (@pxref{insert breakpoint or watchpoint packet}).

+@item bc
+@cindex @samp{bc} packet
+Continue execution in reverse (if capable).
+@xref{Reverse Execution, ,Running programs backward}.
+
+@item bs
+@cindex @samp{bs} packet
+Single step in reverse (if capable).
+@xref{Reverse Execution, ,Running programs backward}.
+
  @item c @var{addr}
  @cindex @samp{c} packet
  Continue.  @var{addr} is address to resume.  If @var{addr} is omitted,