Re:Reverse Debugging and Other Stories
by mark_undoio on Tuesday August 23, 2022 @06:02AM
(#32562572)
There are some points in this article that I don't see mentioned often and are really important benefits.
"Story 1: What if we could let the bug happen and drink a coffee (or more)?" - the fact you can just leave the recorder running until your flaky issue has reproduced is really powerful. Once captured, you can debug at leisure, knowing invisible goblins won't make the problem vanish again.
"Story 2: Let’s print, but not build" - the `dprintf` command in GDB is so cool. Being able to tag additional print commands into the code without having to rebuild is powerful. You can do this iteratively with time travel debug, since you know you're running on the same trace every time.
"Story 1: What if we could let the bug happen and drink a coffee (or more)?" - the fact you can just leave the recorder running until your flaky issue has reproduced is really powerful. Once captured, you can debug at leisure, knowing invisible goblins won't make the problem vanish again.
"Story 2: Let’s print, but not build" - the `dprintf` command in GDB is so cool. Being able to tag additional print commands into the code without having to rebuild is powerful. You can do this iteratively with time travel debug, since you know you're running on the same trace every time.