Reversible Debugging
Scott David Daniels
Scott.Daniels at Acm.Org
Sat Jul 4 08:31:55 EDT 2009
Patrick Sabin wrote:
> Horace Blegg schrieb:
>> You might consider using a VM with 'save-points'. You run the program
>> (in a debugger/ida/what have you) to a certain point (logical point
>> would be if/ifelse/else statements, etc) and save the VM state. Once
>> you've saved, you continue. If you find the path you've taken isn't
>> what you are after, you can reload a previous save point and start
>> over, trying a different path the next time.
> That was my idea to implement it. I thought of taking snapshots of the
> current state every time a "unredoable instruction", e.g random number
> generation, is done.
Remember, storing into a location is destruction.
Go over a list of VM instructions and see how many of them are undoable.
More information about the Python-list
mailing list