Re: reverse trace [was: vmware's replay framework and gdb]

["EBo" <ebo@sandien.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

Thanks Thiago,

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

..

  EBo --


Thiago Jung Bauermann <bauerman@br.ibm.com> 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.  
> <snip>
> > 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
the fly.
> > 
> > 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:
> 
> http://code.google.com/p/chronicle-recorder/
> http://code.google.com/p/chronomancer/
> http://weblogs.mozillazine.org/roc/archives/2007/08/announcing_chro.html
> -- 
> []'s
> Thiago Jung Bauermann
> IBM Linux Technology Center
> 
> 



--