From: Michael Snyder <msnyder@redhat.com>
To: Stan Shebs <shebs@apple.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>, jrydberg@virtutech.com
Subject: Re: [RFC] reverse-step, reverse-next
Date: Fri, 09 Sep 2005 22:39:00 -0000 [thread overview]
Message-ID: <43220F28.70801@redhat.com> (raw)
In-Reply-To: <4320AFFE.9080902@apple.com>
Stan Shebs wrote:
> Michael Snyder wrote:
>
>> This isn't for submission, just for discussion. This is something
>> that Johan Rydberg (of Virtutech) and I have been working on.
>>
>> I'd like to hear what everybody thinks about this
>> bit of infrun implementation for the reverse debugging
>> that we discussed a few months ago.
>>
> Seems plausible to me. I've actually been experimenting with
> a reverse execution prototype based on GDB managing all the
> checkpoints, rather than pushing them down into the target as
> Simics apparently does, and while GDB-managed checkpoints are
> more powerful in some ways (random access to arbitrary states,
> general undo), it's also looking rather more complicated.
Yeah, I consider this sort of abstract and modular.
My patch here makes no assumptions about how a backend
does reverse execution. The backend could, for instance,
call into a separate module such as yours that manages
checkpoints. Another backend might do it by direct request
to the target -- a la Simics.
>> This part is enough to get step and next to work in reverse,
>> based solely on the assumption that the backend (or someone)
>> provides an interface "get_exec_direction ()", which returns
>> forward or reverse. It's also assumed that the backend will
>> know which direction to go (leaving user-interface issues
>> out of the picture). One can imagine either a "set direction"
>> interface, or a "reverse-step/reverse-continue".
>
>
> Presumably there is a set_exec_direction,
Presumably. ;-)
> and both it and
> get_exec_direction are target vector entries?
For instance. But again, this infrun code makes no assumptions.
So that decision is orthogonal -- an implementation detail.
This code would be equally useful whether
(a) the direction was set by a modal "set direction" command,
or
(b) the direction was set by a "reverse-step" command.
> BTW, I have a little discussion of usage models for reverse
> execution that I'm planning to post on Monday.
Looking forward to it.
I, in turn, have a patch to implement "reverse-finish",
which I thought I'd post a little while after this one.
next prev parent reply other threads:[~2005-09-09 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 22:44 Michael Snyder
2005-09-08 21:41 ` Stan Shebs
2005-09-09 22:39 ` Michael Snyder [this message]
2005-09-17 22:19 ` Daniel Jacobowitz
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=43220F28.70801@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jrydberg@virtutech.com \
--cc=shebs@apple.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