Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Reverse debugging, part 1/3: target interface
Date: Wed, 19 Apr 2006 18:26:00 -0000	[thread overview]
Message-ID: <444680C3.1010007@redhat.com> (raw)
In-Reply-To: <u4q0qx85u.fsf@gnu.org>

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

Eli Zaretskii wrote:
>>Date: Tue, 18 Apr 2006 15:08:22 -0700
>>From: Michael Snyder <msnyder@redhat.com>
>>CC: GDB Patches <gdb-patches@sources.redhat.com>
>>
>>>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?
> 
> 
> It's okay, but other packets' descriptions say how to reply to them.
> Can we include that for these two as well?
> 

Good point.  How about this?


[-- Attachment #2: packets --]
[-- Type: text/plain, Size: 953 bytes --]

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.322
diff -u -r1.322 gdb.texinfo
--- gdb.texinfo	14 Apr 2006 18:31:32 -0000	1.322
+++ gdb.texinfo	19 Apr 2006 18:24:30 -0000
@@ -22554,6 +22660,22 @@
 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}.
+
+Reply:
+@xref{Stop Reply Packets}, for the reply specifications.
+
+@item bs
+@cindex @samp{bs} packet
+Single step in reverse (if capable).  
+@xref{Reverse Execution, ,Running programs backward}.
+
+Reply:
+@xref{Stop Reply Packets}, for the reply specifications.
+
 @item c @var{addr}
 @cindex @samp{c} packet
 Continue.  @var{addr} is address to resume.  If @var{addr} is omitted,

  reply	other threads:[~2006-04-19 18:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <442DAA70.5070203@redhat.com>
2006-04-01 12:23 ` Eli Zaretskii
2006-04-17 23:37 ` Michael Snyder
2006-04-18 12:58   ` Daniel Jacobowitz
2006-04-18 15:24     ` Daniel Jacobowitz
2006-04-18 22:08       ` Michael Snyder
2006-04-19  8:48         ` Eli Zaretskii
2006-04-19 18:26           ` Michael Snyder [this message]
2006-04-20  9:18             ` Eli Zaretskii
2006-04-20 13:43             ` Daniel Jacobowitz
2006-04-20 19:22               ` Michael Snyder
2006-04-20 19:50                 ` Daniel Jacobowitz
2006-04-20 23:53                   ` Michael Snyder
2006-04-24 20:55                     ` Daniel Jacobowitz
2006-04-18 18:59     ` Michael Snyder
2006-04-20 13:58 ` Daniel Jacobowitz
2006-04-20 19:42   ` Michael Snyder
2006-04-20 19:58     ` Daniel Jacobowitz
2006-04-01 16:39 Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=444680C3.1010007@redhat.com \
    --to=msnyder@redhat.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox