Re: Using the perl debugger

It's not going to happen. By the time the debugger gets your script, it's already compiled. If you're in a function, there's no way for it to change that function and continue in the changed version. The only thing I can think of that might work is to write a source filter to add labels before every line, then run the debugger on that version of the script, e.g. turn this:

my $x = 23;
die "blaagh!";
[download]

into this:

LINE1: my $x = 23;
LINE2: die "blaagh!"
[download]

then execute a goto in the debugger. Perl's goto is insanely powerful. Unfortunately, you would more or less have to parse the script to do this without introducing syntax errors (think multiline statements), so you're probably hosed.

Comment on Re: Using the perl debugger Select or Download Code

Replies are listed 'Best First'.
Re^2: Using the perl debugger by Anonymous Monk on Mar 30, 2009 at 16:54 UTC
Is there then any way to skip over a line while debugging without previous modification of the script? (that was me asking by the way -- now hopefully logged in)	[reply]
Re^2: Using the perl debugger by avilella (Initiate) on Mar 30, 2009 at 16:55 UTC
(and now finally logged in)	[reply]
Re^3: Using the perl debugger by educated_foo (Vicar) on Mar 30, 2009 at 17:11 UTC
If you've managed to insert the labels, then `goto` should be able to skip to the next line. That said, this whole source filtering thing is a terrible idea. The only decent way to do this would be through XS hacking, and that would take a lot of work.	[reply] [d/l]
Re^2: Using the perl debugger by Anonymous Monk on Mar 30, 2009 at 16:51 UTC
Is there then any way to skip over a line while debugging without previous modification of the script?	[reply]