This is the mail archive of the
mailing list for the GDB project.
Re: reverse trace [was: vmware's replay framework and gdb]
- From: "EBo" <ebo at sandien dot com>
- To: "Thiago Jung Bauermann" <bauerman at br dot ibm dot com>, <ebo at sandien dot com>
- Cc: "Edward Peschko" <horos11 at gmail dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Wed, 5 Nov 2008 22:09:31 MST
- Subject: Re: reverse trace [was: vmware's replay framework and gdb]
- References: <firstname.lastname@example.org>, <email@example.com>
- Reply-to: ebo at sandien dot com
That is so wicked cool! If this project was really ongoing I would be
interested, but as it is it looks orphaned... Who's to know though.
Basically what I was thinking would be behind the scenes with gdb:
* turn reversable tracing on
* step forward
* step back
Thiago Jung Bauermann <firstname.lastname@example.org> said:
> El miÃ©, 05-11-2008 a las 18:01 -0700, EBo escribiÃ³:
> > The overall problem with reverse tracing as I see it is one of caching the old
> > values basically as they change. One way to get at this is to integrate a SQL
> > database with transaction support into the trace subsystem. The you can view
> > the entire history back and forth.
> > Once all this information is funneled through a relational database, you can
> > then either grab the current state of each variable or reconstruct it on
> > Just an idea, and I hope this kind of speculative response is considered
> > acceptable to the group.
> Since we're just brainstorming:
> Have you seen Chronicle and Chronomancer? I didn't try them, but from
> what I read they seem to go in the direction that you suggest here:
> Thiago Jung Bauermann
> IBM Linux Technology Center