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.

Everyone who debugs C/C++ should be using time travel debugging. If you’re not using it, you’re just wasting time.

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.

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.

I put a watchpoint on the memory pointer and worked backwards towards the root cause. I quickly found where the crash happened and why.