Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Julian Smith'" <jsmith@undo-software.com>, 	<gdb@sources.redhat.com>
Subject: RE: Some questions about gdb's remote protocol and reverse  debugging
Date: Fri, 21 Aug 2009 15:43:00 -0000	[thread overview]
Message-ID: <003601ca224e$2fef0ef0$8fcd2cd0$@com> (raw)
In-Reply-To: <20090821084807.5e296baf.jsmith@undo-software.com>


> Ok.
> 
> But... isn't there always going to be a difference when going
> backwards, e.g. if an instruction jumps to an address in a register,
> one cannot know about this jump when stepping backwards (and so, for
> example, one cannot first go back to the destination of the jump, do a
> `bs' to step back over the jump, then carry on with `bc')? Perhaps this
> sort of indirect jump never occurs within a function though, so is not a
> problem for things like reverse-step.
> 
> Anyway, many thanks for you help, 'tis much appreciated. I'm still
> tinkering with things, but i think i should be able to make progress
> now.

Note that you are not executing backwards: you are inspecting what happened. You
do not reverse individual instructions, you are looking at a history. In this
case, of course you can go back forth across jumps, interrupts, returns, and any
other change of location.  How to implement it varies, but either you reexecute
deterministically but one step shorter, or you look into some recorded execution
trace and just move one step back in that. 

/jakob


      reply	other threads:[~2009-08-21 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 23:00 Julian Smith
2009-08-11 23:24 ` Michael Snyder
2009-08-11 23:38   ` Daniel Jacobowitz
2009-08-21 10:57   ` Julian Smith
2009-08-21 15:43     ` Jakob Engblom [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='003601ca224e$2fef0ef0$8fcd2cd0$@com' \
    --to=jakob@virtutech.com \
    --cc=gdb@sources.redhat.com \
    --cc=jsmith@undo-software.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