3 ms·

There is actually a surprising amount of reverse debugging products out there, some are listed here: http://jakob.engbloms.se/archives/1564 http://jakob.engblom

• gautamsomani 4y ago
  Nice link. Thanks for sharing. I took a quick glance and saw that most of them are for embedded systems. Apart from gdb, do you know anything more friendly for Unix and C/C++ programs?
  • pentab 4y ago
    There is undo, I would be very interested in your thoughts on it: https://undo.io/ https://undo.io/ This may also contain further pointers that I missed: https://softwareengineering.stackexchange.com/questions/181527/why-is-reverse-debugging-rarely-used https://softwareengineering.stackexchange.com/questions/1815...
• ok_dad 4y ago
  Hey, thanks for all the references! I looked through there; I code in Python for work (Lua at home a lot), so I didn't see anything that seemed to be targeted towards that use case. I've also seen tools like rr that record a session, but I specifically want to be able to step back and forth while executing code. I would use anything that, at minimum, would allow me to set a "save point" like a breakpoint and then return to that save point from any breakpoint, or from paused execution if I am stepping through the code. I think it would be easier for Python, Lua, or other dynamic, interpreted languages to do this because you could store the program state via storing the interpreter's internal state more easily. Also, I understand side-effects would complicate this and I am willing to ignore those issues if I had a bare-bones reversible debugger for Python.