Reversible debugging tools provider Undo Software's option for its UndoDB reversible debugging tool enables developers to save a program's execution history to a single file, share this resulting Undo Recording with colleagues, or re-load the recording on the same or a different machine at a later date for more detailed analysis. Developers benefit as they can enhance collaboration, increase flexibility by deferring and prioritising when they address the bugs they capture using UndoDB, and reduce usage of expensive or highly contended machines.
UndoDB enables developers to record, rewind and replay their code to quickly find critical bugs, increase productivity and meet development deadlines. The new option extends UndoDB's functionality by creating and saving an Undo Recording. This is a single file containing information that allows UndoDB to completely reconstruct everything a program has done, including every memory access and every instruction executed.
Through Undo’s inter-machine replay technology, the Undo Recording can then be loaded on a different machine to that on which it was saved, and shared with other developers, increasing collaboration. Developers can prioritise the order in which bugs are fixed and jointly debug a particular failure. For example, bugs that have a long run time or strike intermittently can be captured and then preserved for future analysis, without needing to restart the program or reproduce the error, thereby saving time. As Undo Recordings can be saved, UndoDB Save-Load protects against losing data, avoiding the need to spend time re-running the program to reproduce the bug.
The UndoDB Save-Load option enables organisations to reduce usage of expensive or highly contended systems, such as supercomputer nodes, industrial control systems or prototype/bring-up devices, as debugging recordings from these systems can be saved and then loaded onto any UndoDB Save-Load licensed machine running Linux, even if it is running a different Linux distribution.
“Software development is a collaborative process, and UndoDB Save-Load extends this collaboration to the tracking down of bugs, by