2 ms·
The author really should look into rr, a debugger that records the complete execution of the program so you can literally travel backwards in time to see the ro
by fmajid 5y ago
The author really should look into rr, a debugger that records the complete execution of the program so you can literally travel backwards in time to see the root cause of a crash.
https://rr-project.org https://rr-project.org
- teddyh 5y agoNote: gdb also has, for many years, reversible debugging support: https://sourceware.org/gdb/current/onlinedocs/gdb/Reverse-Execution.html#Reverse-Execution https://sourceware.org/gdb/current/onlinedocs/gdb/Reverse-Ex...
- invalidname 5y agoThe ideas of rr aren't new. It's back in time debugging which is great but sometimes a bit of a bother. E.g. with a regular debugger you can change a value, move the stack and reproduce the issue differently to help inform/verify. With back in time debuggers you're restricted to the current capture. But I do agree that rr is cool and worth knowing.