From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: ebo@sandien.com
Cc: Edward Peschko <horos11@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: reverse trace [was: vmware's replay framework and gdb]
Date: Thu, 06 Nov 2008 04:45:00 -0000 [thread overview]
Message-ID: <1225946634.20764.74.camel@localhost.localdomain> (raw)
In-Reply-To: <twig.1225933292.67320@swcp.com>
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
next prev parent reply other threads:[~2008-11-06 4:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 19:05 vmware's replay framework and gdb Edward Peschko
2008-11-06 1:02 ` reverse trace [was: vmware's replay framework and gdb] EBo
2008-11-06 4:45 ` Thiago Jung Bauermann [this message]
2008-11-06 5:10 ` EBo
2008-11-06 10:22 ` Jakob Engblom
2008-11-06 17:01 ` EBo
2008-11-06 17:09 ` Jakob Engblom
2008-11-06 1:21 ` vmware's replay framework and gdb Michael Snyder
2008-11-06 10:25 ` Jakob Engblom
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=1225946634.20764.74.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=ebo@sandien.com \
--cc=gdb@sourceware.org \
--cc=horos11@gmail.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