Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Julian Smith <support@undo-software.com>
To: gdb@sources.redhat.com
Subject: Re: Return to Reverse Execution
Date: Tue, 16 May 2006 20:24:00 -0000	[thread overview]
Message-ID: <20060516201833.2a6ba688.support@undo-software.com> (raw)
In-Reply-To: <43BC376F.4000307@redhat.com>

On Wed, 04 Jan 2006 13:00:31 -0800
Michael Snyder <msnyder@redhat.com> wrote:

> Over the past several months, there's been some great discussion
> of this topic, and even some trial patches sent out for comment.
> 
> I'd like to start preparing a real submission for approval.
> I'm testing the waters now, to see how close we may be to
> converging on an acceptable interface spec.
> 
> So here is my proposed gdb user interface.

We've been busy the past year or so making such a "reverse execution"
engine (we call it a bidirectional debugger).  It's debugger neutral,
but our first supported front end is gdb.  As such we've patched gdb-6.4
to provide support for our new commands.  Communication between gdb and
the bidirectional debugger engine is via a pair of FIFOs.

You can check it out at http://undo-software.com/


>    1) A set of new commands that mimic the existing ones,
>    to include:
> 	reverse-step (rs)
> 	reverse-next (rn)
> 	reverse-continue (rc)
> 	reverse-finish (rf)

We decided on using a `b' prefix to existing execution commands: bnext,
bnexti, bstep, bstepi, buntil and bfinish.  There are also new commands:
`bgoton' goes back to an arbitrary temporal position, `bgoto' goes back
to an arbitrary place (e.g. `bgoto foo.c:23') and `bget' displays the
current temporal position.

If gdb develops a set of standard commands, we'd definitely use them.
The above ones seem to work well, but might not cover all types of
reverse execution engines.

- Julian

-- 
http://undo-software.com/


      parent reply	other threads:[~2006-05-16 19:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 21:01 Michael Snyder
2006-01-05  5:04 ` Eli Zaretskii
2006-01-06  4:28   ` Michael Snyder
2006-01-06  9:02     ` Eli Zaretskii
2006-01-06 15:19       ` Paul Koning
2006-01-13 16:02         ` Bob Rossi
2006-01-13 19:43           ` Eli Zaretskii
2006-01-06 10:30     ` Dave Korn
2006-01-06 11:17       ` Eli Zaretskii
2006-01-06 12:29         ` Dave Korn
2006-01-06 14:09           ` Eli Zaretskii
2006-01-06 14:12           ` Eli Zaretskii
2006-01-06 16:59           ` Dave Brolley
2006-01-06 19:57 ` Daniel Jacobowitz
2006-01-06 21:51   ` Paul Gilliam
2006-01-06 21:53     ` Daniel Jacobowitz
2006-01-06 22:05       ` Paul Gilliam
2006-01-09  8:41 ` Vladimir Prus
2006-05-16 20:24 ` Julian Smith [this message]

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=20060516201833.2a6ba688.support@undo-software.com \
    --to=support@undo-software.com \
    --cc=gdb@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