It's unnecessary but true: a lot of Java programmers still debug by putting
System.out.println() statements in their code to find out what the program is
really doing and where the problems are. To overcome this antiquated approach
I've tried several debuggers: Sun's JDB is free but cumbersome and hard to
work with. Visual SlickEdit, my favorite IDE, has integrated debugger support
but is also difficult to run. Metamata debugger was my next choice but the
product went away. So I searched the Web for options and, indeed, there is a
better way: RetroVue from VisiComp. It creates a complete journal of your
program's execution, letting you go back to any previous instance and examine
the state back then. These features and some articles about "Omniscient
Debugging" aroused my interest in RetroVue.
In this article I try to explain the difference between RetroVue and other... (more)