Your guide to UDB and LiveRecorder
This documentation explains how to use UDB - a powerful time travel debugger for Linux based applications, and LiveRecorder - Undo’s flagship product platform for rapid software defect diagnosis & resolution.
UDB allows you to go back to any point in the debuggee’s execution history, including stepping backwards and forwards by individual instructions, source lines, function calls and so on. It can regenerate the complete state of the debuggee process at any point in its execution, including information that is destroyed during execution.
The LiveRecorder library which can be used by any Linux application to give it self-recording capabilities.
The live-record command-line tool which records the execution of a process.
- Release 6.8
Parallel Search - a performance-enhancement option that makes use of multi-core systems to improve the performance of reverse navigation commands - enabled in UDB by default.
Faster saving and loading of LiveRecorder recordings via LZ4 compression.
- Release 6.7
UDB displays a progress indicator when loading LiveRecorder recordings.
Upgraded the version of Python that is packaged with UDB and that is used by C++ pretty-printers from 3.6 to 3.10.
Dropped support for RHEL & CentOS 6.
- Release 6.6
Parallel Search - a performance-enhancement option that makes use of multi-core systems to improve the performance of reverse navigation commands. The speed-up achieved will depend on how far back in history the command moves; the more history executed, the greater the benefit.
While performing a reverse execution command (including reverse-step, reverse-next and the corresponding Reverse Step Into and Reverse Step Out buttons in Visual Studio Code) UDB will stop the program’s execution if the program hits a breakpoint or watchpoint.
The stepi and reverse-stepi commands now step one instruction forwards or backwards within the current thread. You can also use
reverse-stepi -any-threadto step back exactly one instruction back in history, potentially switching threads in the process.
Added the delete bookmark command for deleting bookmarks.
- Release 6.5
Added syntax highlighting for source code displayed by UDB, for instance when stopping at a breakpoint, when invoking the
listcommand, or in TUI mode.
Added support for debuginfod in UDB. This allows UDB to fetch debug info and source code from debuginfod servers specified with the space-separated environment variable
Reverse commands now uniformly respect the same arguments (repeat count) and context (current frame) as their forwards equivalents.
Upgraded the version of GDB that is packaged with UDB from 9.2 to 10.2. Details of the various bugs that this fixes can be found at GDB News .
Deprecated all commands starting with the
uclearprefixes in favour of the equivalent GDB prefixes:
Prefixes which don’t have a GDB equivalent, like
ugo, were not renamed.
- Release 6.4
Status Prompt: UDB’s prompt displays the status of the debugged program and the progress through its execution history.
Undo/Redo: New UDB commands ugo undo (
ur) support undoing and redoing navigation and time-travel commands.
Changed the default UDB event log mode to
circular. This means that when the event log reaches its maximum size, old events are dropped to make room for new ones, allowing the program to continue running.
[Beta] Time Travel Debug for C/C++ extension for Visual Studio Code. Enables UDB’s time travel debugging capabilities in Microsoft’s enormously popular Visual Studio Code (VS Code) editor. Download the extension from Undo’s Community Forum.
Reverse step commands (
reverse-until) remain in the same thread and are more consistently performant. The
reverse-stepicommands can still be used to forward or reverse step single instructions while following thread switches.
[Experimental] A replay-time option provides 2-6x speedup by exploiting multiple CPU cores when performing reverse navigation commands including
- Release 6.3
Bookmarks that you place when replaying a LiveRecorder recording in UDB are automatically persisted across debugging sessions.
UDB displays a progress indicator when performing a long-running time travel operation.
Further improved the performance of the
reverse-nextcommand and other reverse operations, and improved the correctness of these operations when debugging highly optimized code.
UDB now uses styles and colours in the text printed at startup.
- Release 6.2
Improved performance of reverse operations in a number of situations including long-running operations and operations which stay in the same thread.
Deprecated all command line options starting with
--undodb-in favour of options without any prefix. Refer to the
changelog.txtfile or product documentation for details.
- Release 6.1
UDB is the new name for UndoDB. Existing
--undodbcommand-line options will be retained for 6.x releases.
Upgraded the version of GDB that is packaged with UDB from 8.1 to 9.2. New GDB features, such as new commands and styled output, are described at GDB News under the relevant sections.
Upgraded the version of Python that is packaged with UDB and that is used by C++ pretty-printers from 2.7 to 3.6. Python 2 only pretty printers shipped by older supported distros are converted automatically at load time into Python 3.
The Log Jump feature is now enabled for all existing and new UDB and LiveRecorder customers.
- Release 6.0
Support for applications written in the Java language.
Recordings are portable across machines with different CPU microarchitectures. See Recording Portability for details.
Core engine 25%-100% faster than 5.0 on diverse workloads.