Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: teawater <teawater@gmail.com>,
	"Jakob Engblom" <jakob@virtutech.com>,
	 	"Michael Snyder" <msnyder@vmware.com>,
	gdb@sourceware.org
Subject: Re: [discuss] semantics, "replay debugging" vs. "reverse debugging"
Date: Wed, 22 Oct 2008 16:19:00 -0000	[thread overview]
Message-ID: <daef60380810220918i3e3e1493mdd4af64ff919ac08@mail.gmail.com> (raw)
In-Reply-To: <20081022133716.GA10237@caradoc.them.org>

I think your mean that add is a X86 instruction or ARM insn. But some
arch's add not set flag such as MIPS.

addiu $1, $1, 10

It not set anything except $1.

And I said add insn just a example, I am not say for each arch and
each insn? just some of them.



On Wed, Oct 22, 2008 at 21:37, Daniel Jacobowitz <drow@false.org> wrote:
>
> On Wed, Oct 22, 2008 at 11:25:17AM +0800, teawater wrote:
> > I think your not clear my idea.
> >
> > > 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.
> >
> > Maybe you can read this part again.
> >
> > And what is the status of program? Most of time, it's just the values
> > of registers and memory. Do not think anything that complex.
>
> Jakob is right.  For instance, if the add instruction sets an overflow
> flag in the status register, you can not figure out what the previous
> version of the overflow flag was after the instruction.
>
> --
> Daniel Jacobowitz
> CodeSourcery


  reply	other threads:[~2008-10-22 16:19 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
2008-10-22  3:26     ` teawater
2008-10-22 13:37       ` Daniel Jacobowitz
2008-10-22 16:19         ` teawater [this message]
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=daef60380810220918i3e3e1493mdd4af64ff919ac08@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=jakob@virtutech.com \
    --cc=msnyder@vmware.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