From: Daniel Jacobowitz <drow@false.org>
To: Itzhak Ben-Akiva <benakiva@gmail.com>,
Michael Snyder <Michael.Snyder@palmsource.com>
Cc: gdb@sourceware.org
Subject: Re: Reversible Debugging
Date: Mon, 08 Jan 2007 22:36:00 -0000 [thread overview]
Message-ID: <20070108223606.GA28658@nevyn.them.org> (raw)
In-Reply-To: <f6df51f00701081230k37e2c500yf05212ddaee5baff@mail.gmail.com>
On Mon, Jan 08, 2007 at 10:30:33PM +0200, Itzhak Ben-Akiva wrote:
> Hi all,
>
> I read on http://www.fsf.org/campaigns/priority.html - High Priority
> Free Software Projects that the GDB maintainers are looking for
> contributors interested in expanding the foundations of reversible
> debugging to GDB. I'm very interested in taking over this project. Is
> there anyone already working on it? I'll start by read the project's
> documentation and the patches released. However, I would appreciate
> any suggestions or guidance on how to start.
>
> I'd appreciate any comments or suggestions.
Welcome! No one is currently working on it; the patches I know of are
either included in the current CVS HEAD version of GDB (for fork-based
checkpoints on GNU/Linux), or posted to the gdb-patches mailing list.
Search for "reverse" in the archives during March and April 2006 to
find support for reverse execution commands which work with a remote
simulator target which supports reverse execution. As you can tell
from the patches, Michael Snyder did all of that work.
There's also support for reverse simulation of the xstormy16 target
using Red Hat's "sid" simulator, posted to the sid and GDB lists in
September 2006.
That's about where we stand today. Where we go from here is unclear -
this message and the news post you followed contain just about
everything I know on the subject.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-08 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 20:30 Itzhak Ben-Akiva
2007-01-08 22:36 ` Daniel Jacobowitz [this message]
2007-01-09 6:54 ` Itzhak Ben-Akiva
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=20070108223606.GA28658@nevyn.them.org \
--to=drow@false.org \
--cc=Michael.Snyder@palmsource.com \
--cc=benakiva@gmail.com \
--cc=gdb@sourceware.org \
/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