Re^3: Neat Debugger tricks

I understand what you are trying to do...identify a bug, modify the code, and continue debugging with the modified code. That would be very nice.

Yes, yes, yes, and yes :-)

Microsoft Visual Studio does this, at least for c, and Eclipse does it for Java. These are languages where you'd expect these things to be waaaay harder to get away with than Perl. (Well, except for "set next instruction", which in c is relatively easy.)

Comment on Re^3: Neat Debugger tricks

Replies are listed 'Best First'.
Re^4: Neat Debugger tricks (rerun command) by ysth (Canon) on Nov 18, 2005 at 05:04 UTC
Your wish is granted (in 5.8.5): $ perl -de0 Loading DB routines from perl5db.pl version 1.28 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. main::(-e:1): 0 DB<1> h rerun rerun Rerun session to current position. rerun n Rerun session to numbered command. rerun -n Rerun session to number'th-to-last command. [download] rerun reloads the program and applies all commands you've executed in the debugger to (theoretically) get you back to the same point.	[reply] [d/l]
Re^5: Neat Debugger tricks (rerun command) by gaal (Parson) on Nov 18, 2005 at 09:14 UTC
That's very nice, and has many uses, but isn't what I was wishing for. That's a replay of the complete flow. I want the option to goto an arbitrary line in the code of a running process. Sure, it's not obvious what that means when there are e.g. closures in effect, but I guess that's something to figure out.	[reply]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks