From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [discuss] going back: reverse-execution vs. checkpoint/restart
Date: Mon, 23 May 2005 19:01:00 -0000 [thread overview]
Message-ID: <20050523190111.GA9003@nevyn.them.org> (raw)
In-Reply-To: <42922617.3050805@redhat.com>
On Mon, May 23, 2005 at 11:51:03AM -0700, Michael Snyder wrote:
> And it's quite reasonable to suppose that there is an
> evolutionary path from checkpoint/restart to reverse
> execution. We've already discussed some of the ways
> in which it could go, so I think it's virtually a given
> that it is possible to get from A to B. For that matter,
> it should be also possible to get from B to A: a target
> that only supports the rs/bs primatives should be able
> to implement checkpoint/restart in terms of them.
Not necessarily. Once you back up and manually make a state change it
may not be possible to get back to some other state previously reached.
> How much of that evolution needs to take place on the
> gdb side, and how much on the target side, is a great
> field for discussion -- I would only note that we do
> not have to answer that question now. If we convince
> ourselves that both sets of primatives are useful for
> some targets, and that one may evolve into the other,
> then there is no reason not to implement them both.
> Being able to do either one but not the other would
> be better than not being able to do either.
Thank you, Michael - that's what I was trying to suggest, but not very
well.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-23 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 18:51 Michael Snyder
2005-05-23 19:01 ` Daniel Jacobowitz [this message]
2005-05-23 19:15 ` Michael Snyder
2005-05-23 19:32 ` Dan Shearer
2005-05-23 19:37 ` Dan Shearer
2005-05-24 4:47 Paul Schlie
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=20050523190111.GA9003@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=msnyder@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