> With the debugger, you can only see the application state at one specific point at the time.
Really depends on the debugger. Some tools support “time travel” debugging, which essentially stores a structured log of memory state over time.
Really depends on the debugger. Some tools support “time travel” debugging, which essentially stores a structured log of memory state over time.
(That wasn't what I wanted to post; I should have waited.)
More like stop the flow of time, fix whatever went wrong, fix why it went wrong, go back before it happened, and then restore time flow, as if nothing had happened (so more restart before than resume after).
I don't know if that's what the OP wanted or not, I'll leave you to explain.