Discussion:
[funsec] Debugging Backwards in Time (fwd)
Gadi Evron
2007-03-22 14:30:26 UTC
Permalink
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 <***@computerbytesman.com>
To: 'FunSec LList' <***@linuxbox.org>
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
"continue" one too many times... What if you could simply go backwards to
see what went wrong? This is the essence of the "Omniscient Debugger" -- it
remembers everything that happened during the run of a program, and allows
the programmer to "step backwards in time" 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 "ODB"
-- 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 "navigate" 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
<http://www.gbcacm.org/website/www.LambdaCS.com> site
Peter Ferrie
2007-03-22 16:13:12 UTC
Permalink
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:***@linuxbox.org]
Sent: Thu 3/22/2007 7:30 AM
To: code-***@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 <***@computerbytesman.com>
To: 'FunSec LList' <***@linuxbox.org>
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
"continue" one too many times... What if you could simply go backwards to
see what went wrong? This is the essence of the "Omniscient Debugger" -- it
remembers everything that happened during the run of a program, and allows
the programmer to "step backwards in time" 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 "ODB"
-- 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 "navigate" 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
<http://www.gbcacm.org/website/www.LambdaCS.com> site
Rodrigo Rubira Branco (BSDaemon)
2007-03-22 16:54:31 UTC
Permalink
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 <***@symantec.com>
Para: code-***@whitestar.linuxbox.org
<code-***@whitestar.linuxbox.org>
Assunto: Re: [Code-Crunchers] [funsec] Debugging Backwards in Time (fwd)
Data: 22/03/07 14:14
Post by Peter Ferrie
http://weblogs.mozillazine.org/roc/archives/2006/12/introducing_amb.html
http://www.ocallahan.org/Amber.pdf
________________________________
Sent: Thu 3/22/2007 7:30 AM
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
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
Post by Peter Ferrie
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
Post by Peter Ferrie
see what went wrong? This is the essence of the &quot;Omniscient
Debugger&quot; -- it
Post by Peter Ferrie
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
Post by Peter Ferrie
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;
Post by Peter Ferrie
-- an implementation of Omniscient Debugging for Java programs -- and
discuss the various costs and trade-offs. The last half of the talk will
be
Post by Peter Ferrie
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
Post by Peter Ferrie
program was doing, where values were set, when various threads ran, etc.
At
Post by Peter Ferrie
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%
Post by Peter Ferrie
pure Java and has been tested under Solaris, MacOS, and Windows. It is
freely available at Bil's web
_______________________________________________
Code-Crunchers mailing list
http://whitestar.linuxbox.org/mailman/listinfo/code-crunchers
________________________________________________
Message sent using UebiMiau 2.7.2

Loading...