Omniscient Debugging - Next Generation Debugging
Our aim is to produce a debugger that can control not only the flow of execution but one that can control the direction of execution. Yes, a Debuggger that not only step forwards but one that can also step backwards (in time!).
Motivation:
The first debugger DDT(http://www.elook.org/computing/ddt.htm) came out in 1961. One look at the commands(http://web.mit.edu/afs/net/project/cgw/src/ddt.68/ddt.cmds) will reveal that it has the same features of the contemperory debuggers of today. How is that bad? Because not many people(Good programmers to the very least) don't use debuggers. Notably, an informal survey (a show of hands in conferences, classes, etc.) of several thousand programmers reveals that roughly 90% of all programmers debug their programs strictly by use of println()!