Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: "'teawater'" <teawater@gmail.com>,
		"'Michael Snyder'" <msnyder@vmware.com>
Cc: <gdb@sourceware.org>
Subject: RE: [discuss] semantics, "replay debugging" vs. "reverse debugging"
Date: Tue, 21 Oct 2008 07:29:00 -0000	[thread overview]
Message-ID: <007e01c9334e$aad56ff0$00804fd0$@com> (raw)
In-Reply-To: <daef60380810200907x75bc1661k6d8f5b82e43d7d38@mail.gmail.com>


> > One could have reverse without record/replay if,
> > for instance, one had a machine architecture where
> > all instructions were reversable, ie. the machine
> > itself could reverse-execute an instruction.
> 
> I think maybe some instruction can do it.
> Such as add instruction. When it forward execute, it add some number
> to a value of register. When it reverse, it can sub this number from
> the value of register. It can reverse without record.
> 
> In P record, I make a interface to use it in record_t need_dasm. But I
> still not use it. Maybe I can use it in the future.

When thinking about overflow semantics, etc., it is clear that this can never
work in general.  

The easiest way to create a reversible system is to 

1. Impose determinisim

2. Make sure you can get back to a previous state

And then you simply jump back and reexecute until some chosen point in time.
Works like a charm, and is very general.

/jakob


  reply	other threads:[~2008-10-21  7:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  1:14 Michael Snyder
2008-10-20  8:11 ` Frederic Riss
2008-10-20 16:08 ` teawater
2008-10-21  7:29   ` Jakob Engblom [this message]
2008-10-22  3:26     ` teawater
2008-10-22 13:37       ` Daniel Jacobowitz
2008-10-22 16:19         ` teawater
2008-10-22 16:43           ` teawater
2008-10-22 16:48             ` teawater
2008-10-22 17:09             ` Dave Korn
2008-10-22 17:19               ` teawater
2008-10-22 18:14             ` Michael Snyder
2008-10-22 19:38               ` Jakob Engblom
2008-10-23  3:46                 ` teawater
2008-10-23  8:35                   ` Jeremy Bennett
2008-10-23 10:43                   ` Jakob Engblom
2008-10-23  3:39               ` teawater
2008-10-21  7:27 ` Jakob Engblom

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='007e01c9334e$aad56ff0$00804fd0$@com' \
    --to=jakob@virtutech.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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