[Code-Crunchers] [funsec] Debugging Backwards in Time (fwd)

[Rodrigo Rubira Branco (BSDaemon)]

http://sources.redhat.com/gdb/news/reversible.html

--
http://www.kernelhacking.com/rodrigo

Kernel Hacking: If i really know, i can hack

GPG KeyID: 5E90CA19


--------- Mensagem Original --------
De: Peter Ferrie <pferrie at symantec.com>
Para: code-crunchers at whitestar.linuxbox.org
<code-crunchers at whitestar.linuxbox.org>
Assunto: Re: [Code-Crunchers] [funsec] Debugging Backwards in Time (fwd)
Data: 22/03/07 14:14

>
> Cool.  Along the same lines:
>
>
> http://weblogs.mozillazine.org/roc/archives/2006/12/introducing_amb.html
>
> http://www.ocallahan.org/Amber.pdf
>
>
>
> ________________________________
>
> From: Gadi Evron [mailto:ge at linuxbox.org]
> Sent: Thu 3/22/2007 7:30 AM
> To: code-crunchers at whitestar.linuxbox.org
> Subject: [Code-Crunchers] [funsec] Debugging Backwards in Time (fwd)
>
>
>
> Erm..
>
> I don't get a word this says, but I think he speaks of run-time analysis.
>
> ---------- Forwarded message ----------
> Date: Thu, 22 Mar 2007 10:28:11 -0400
> From: Richard M. Smith &lt;rms at computerbytesman.com&gt;
> To: 'FunSec LList' &lt;funsec at linuxbox.org&gt;
> Subject: [funsec] Debugging Backwards in Time
>
> http://www.gbcacm.org/website/semInfo.php?id=1125
>
> What if a debugger could allow you to simply step BACKWARDS? Instead of
all
> that hassle with guessing where to put breakpoints and the fear of typing
> &quot;continue&quot; one too many times... What if you could simply go
backwards to
> see what went wrong? This is the essence of the &quot;Omniscient
Debugger&quot; -- it
> remembers everything that happened during the run of a program, and allows
> the programmer to &quot;step backwards in time&quot; to see what happened
at any point
> of the program. All variable values, all objects, all method calls, all
> exceptions are recorded and the programmer can now look at anything that
> happened at any time. In this talk, I will describe the design of the
&quot;ODB&quot;
> -- an implementation of Omniscient Debugging for Java programs -- and
> discuss the various costs and trade-offs. The last half of the talk will
be
> a demonstration of the ODB, showing how the various pieces of data are
> displayed and how the programmer can &quot;navigate&quot; through time to
see what the
> program was doing, where values were set, when various threads ran, etc.
At
> the conclusion of the talk, the audience will be invited to use the ODB to
> find some actual bugs. Anyone having a laptop with Java on it can download
> the ODB (beforehand!) and try using it to find the bugs themselves.
>
>
>
> The ODB is an experimental program under development. It is written in
100%
> pure Java and has been tested under Solaris, MacOS, and Windows. It is
> freely available at Bil's web
> &lt;http://www.gbcacm.org/website/www.LambdaCS.com&gt; site
>
>
>
> _______________________________________________
> Code-Crunchers mailing list
> Code-Crunchers at whitestar.linuxbox.org
> http://whitestar.linuxbox.org/mailman/listinfo/code-crunchers
>
>
>
>
>
>

________________________________________________
Message sent using UebiMiau 2.7.2