2009/7/4 Patrick Sabin :
> If someone has another idea of taking a snapshot let me know. Using VMWare
> is not a
> very elegant way in my opinion.
Someone implemented the same idea for Java a while ago. They called it
"omniscient debugging"; you can find details at
http://www.lambdacs.com/debu
Now, if the snapshot is a feature of the Python VM, that's another
matter entirely.
I thought of taking a snapshot using fork, which creates a copy of the
process. It may not be the
most performant, but it should be quite portable. Of course there are
some issues with
multithreading/multiproc
Steven D'Aprano wrote:
On Sat, 04 Jul 2009 09:58:39 -0400, Dave Angel wrote:
Read his suggested approach more carefully. He's not "undoing"
anything. He's rolling back to the save-point, and then stepping
forward to the desired spot. Except for influences outside his control
(eg. file s
Dave Angel wrote:
Scott David Daniels wrote:
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. On
On Sat, 04 Jul 2009 09:58:39 -0400, Dave Angel wrote:
> Read his suggested approach more carefully. He's not "undoing"
> anything. He's rolling back to the save-point, and then stepping
> forward to the desired spot. Except for influences outside his control
> (eg. file system operations), this
Scott David Daniels wrote:
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,
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
Patrick Sabin wrote:
Hello,
I am interested if there are any python modules, that supports
reversible debugging aka stepping backwards. Any links or ideas would
be helpful, because I am thinking of implementing something like that.
In some cases it would be nice to have something like that
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'
Gabriel Genellina schrieb:
Do you want reverse execution, like an undo function? Undo all changes
made by executing some piece of code?
I am not completly sure, if I really want to make exact undo, i.e.
undoing commands by reversing all their effects, or just restoring the
program state to an ar
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
En Fri, 03 Jul 2009 15:18:51 -0300, Patrick Sabin
escribió:
I am interested if there are any python modules, that supports
reversible debugging aka stepping backwards. Any links or ideas would be
helpful, because I am thinking of implementing something like that.
Do you want reverse
Hello,
I am interested if there are any python modules, that supports
reversible debugging aka stepping backwards. Any links or ideas would be
helpful, because I am thinking of implementing something like that.
Thanks in advance,
Patrick
--
http://mail.python.org/mailman/listinfo/python-list
13 matches
Mail list logo
