NEW RESEARCH REPORT: Overcoming the limitations of coding agents in complex software systems

Learn more

Products

Pricing

Solutions

Customers

Resources

Company

Free trial

See a demo

Products

Pricing

Solutions

Customers

Resources

Company

Free trial

See a demo

Find and fix C/C++ bugs in minutes with UDB

Download now

UDB

The interactive time travel debugger for Linux C/C++ for debugging live processes

Attach UDB to a running process, record the execution, and replay that execution history to get instant visibility into what the process just did, and why. No more guesswork!

Travel back and forth in the recording to inspect program state at any point in the execution history.

Simply follow the trail from symptom to root cause in a single debug cycle – cutting out the multiple debug iterations and saving you tons of time!

Ideal for quickly debugging all types of bugs – especially the hardest ones which remain unresolved for months, or take days to diagnose including:

Race conditions
Deadlocks
Memory corruptions
Segfaults
Stack corruptions

Also used for quickly understanding code you didn’t write.

How does it work?

UDB delivers the full power of a modern debugger with variable and memory inspection, scripting, conditional breakpoints and watchpoints – all available in forward and reverse directions.

UDB CAN BE USED IN 2 WAYS

Start a process in UDB

Use the run command in UDB to run the program or follow these instructions in VS Code

Attach UDB to a running process

Attach UDB to an existing process using the udb --pid PID command-line option or from the Run menu in VS Code, select Add Configuration, and then C/C++: (UDB) Attach.

Watch below how it works

100% compatible with GDB, so no need to learn a new tool – just a handful of new commands. Also available as a VS Code extension or CLion plugin.

Key features

GDB COMPATIBLE

If you’re already familiar with GDB, it’s just a handful of new commands to unleash the power of time travel.

See Quick Reference Guide →

IDE INTEGRATION

Integrate UDB into Visual Studio Code to debug directly from your preferred IDE. View the documentation for more information. You can also use UDB in CLion, Eclipse, and Emacs.

NO EXTRA SET UP REQUIRED

No compilation or build changes required. No kernel or system configuration.

What software engineers say

“
When dealing with unfamiliar code, there is a huge productivity benefit in being able to go backwards and forwards over the same section of code until you fully understand what it does.
Rob Thompson
Senior Software Engineer, Siemens EDA
“
Everyone who debugs C/C++ should be using time travel debugging. If you’re not using it, you’re just wasting time.
Brian Janes
Senior Engineering Director, High Performance Computing at Altair
“
UDB has helped us efficiently diagnose numerous challenging issues that would have taken much more time to resolve with GDB or other debuggers that are forward-looking with little or no reversibility.
Ed Klotz
Senior Software Scientist, IBM CPLEX R&D
“
We experienced unexpected rejections from the exchange on orders that we have been sending for years—without any software changes on our end. With Undo, it took me just 1 hour to diagnose the issue, allowing us to get a quick workaround and resume trading this product before our competitors were able to act.
Software Engineer
Trading Firm
“
Using UDB, I was able to step backwards in time in the current thread of execution to get to the last known good state. From there, I did a binary search through the intervening time to pinpoint when different pieces of the state changed and uncovered what code was responsible for those changes.
Senior software engineer
Leading database and analytics platform provider
“
I put a watchpoint on the memory pointer and worked backwards towards the root cause. I quickly found where the crash happened and why.
Routing software developer
Global networking provider

“
When dealing with unfamiliar code, there is a huge productivity benefit in being able to go backwards and forwards over the same section of code until you fully understand what it does.
Rob Thompson
Senior Software Engineer, Siemens EDA
“
Everyone who debugs C/C++ should be using time travel debugging. If you’re not using it, you’re just wasting time.
Brian Janes
Senior Engineering Director, High Performance Computing at Altair
“
UDB has helped us efficiently diagnose numerous challenging issues that would have taken much more time to resolve with GDB or other debuggers that are forward-looking with little or no reversibility.
Ed Klotz
Senior Software Scientist, IBM CPLEX R&D
“
We experienced unexpected rejections from the exchange on orders that we have been sending for years—without any software changes on our end. With Undo, it took me just 1 hour to diagnose the issue, allowing us to get a quick workaround and resume trading this product before our competitors were able to act.
Software Engineer
Trading Firm
“
Using UDB, I was able to step backwards in time in the current thread of execution to get to the last known good state. From there, I did a binary search through the intervening time to pinpoint when different pieces of the state changed and uncovered what code was responsible for those changes.
Senior software engineer
Leading database and analytics platform provider
“
I put a watchpoint on the memory pointer and worked backwards towards the root cause. I quickly found where the crash happened and why.
Routing software developer
Global networking provider

Want unlimited record capabilities, portable recording files, integrations, and capture bugs in production?

UDB is perfect for individual developers.

But if you want unlimited record capabilities, portable recording files to replay any time anywhere, integrations with your CI or test automation suite, or capture bugs in production as well as support for other languages, check out the full Undo Suite for teams.

Common questions

UDB runs on most modern Linux distributions and supports both 32 and 64-bit x86 programs. For more details, see the full list of system requirements at docs.undo.io/SystemRequirements.html.