I know there are some products for reverse debugging.
I am wondering that does reverse debugging mean going to one step back or starting over again up to one step back?
I've found an explanation here.
-
2I can't tell you if it means "really debugging backwards" because I don't know what you mean by "really debugging backwards" ;-)user7043– user70432013-04-16 16:49:39 +00:00Commented Apr 16, 2013 at 16:49
-
2@delnan: He means "does it reverse the previous step or does it run from the beginning with a virtual breakpoint on the previous line."pdr– pdr2013-04-16 16:54:16 +00:00Commented Apr 16, 2013 at 16:54
-
1Reverse debugging is putting the bugs back in.Anthony Pegram– Anthony Pegram2013-04-16 16:59:10 +00:00Commented Apr 16, 2013 at 16:59
-
1Are you thinking of the omniscient debugger?user40980– user409802013-04-16 17:00:34 +00:00Commented Apr 16, 2013 at 17:00
Add a comment
|
1 Answer
does reverse debugging mean going to one step back or starting over again up to one step back?
According to the link you posted, "reverse debugging" means being able to undo instructions in the debugger. So you'd have something like a 'step back' command that tells the debugger to reverse the effect of the last instruction executed. It doesn't mean re-running the program to get back to the previous instruction.
