The Best of 2015 Electronic Design choice for software is often a challenge because of improvements, but this year one stands out.
“It failed, but how did I get here?” This is a typical lament of a developer using a debugger when a program fails. Usually a breakpoint can be set after the fact or well before, but pinpointing where and how a failure occurs is often as much art as it is skill. That was until Undo Software developed UndoDB, a reverse-execution debugging tool. Undo Software’s UndoDB is a trace-based debugging tool that allows replaying of execution and data for almost any application in using debug platforms like the Eclipse IDE (see the figure).
UndoDB essentially instruments an application, allowing it to trace the execution of the program. This log is stored and then replayed by the enhanced debugger that knows about the UndoDB log file. It can step forward or backward. This is similar to many trace/debug facilities that can move backwards and forward through the execution list.
The difference is that UndoDB tracks data operations as well and can present the contents of registers and memory values. This means it can also scan and set breakpoints associated with data. For example, if the program stops when a bad value is detected it is possible to backtrack to determine when the value was changed and even examine other values that might have been used to compute the bad value.
The typical overhead for using UndoDB is about 1.7. The system can handle multicore systems that use shared memory. It can also handle multiple threads.
Finding bugs can be a difficult task, but UndoDB can greatly reduce the time to find the root cause of an application.
