Attach/detach debugger from running program

The old perltodo notes "With gdb, you can attach the debugger to a run
+ning
program if you pass the process ID. It would be good to do this with t
+he
Perl debugger on a running Perl program, although I'm not sure how it 
+would
be done." ssh and screen do this with named pipes in /tmp. Maybe we ca
+n too.
[download]

It's clearly a technique that many would love to have.  As far as I know, though, it hasn't been implemented yet.

Thanks for the info, I thought I'm just missing something, as such functionality is/would be immensly usefull.

FWIW: I'm trying...

As noted in Devel::STrace: strace for Perl scripts (with some seedlings), Devel::STrace et al. provide the seeds to support an attachable debugger. I'm hoping to get one together within a month or so.

It will also be browser based, and multithread/multiprocess friendly...and (hopefully) collaborative.

Alas, that doesn't solve your problem today <sigh/>

If you're willing to roll up your sleeves, you might be able to either hack up Devel::STrace/Devel::RingBuffer to achieve what you need, or maybe wire something together with Devel::ebug.

Unless it's started with debugging enabled, no I don't think there's a way to get an existing process into the debugger. However having said that you probably could come up with a creative combination of PERLDB_OPTS and a subroutine which you trigger somehow (say sending your process a SIGUSR1) that sets $DB::signal to make it so that you can get it to drop into the debugger on demand rather than from the start. See perldebtut, perldebug, and perldebguts for more hints (and I don't want to hear any complaints about performance if you run everything under the debugger :).

(And as a parenthetical aside, it'd be cool if there was some way to do something in Perl akin to the Ruby on Rails breakpoint / script/breakpointer setup. That lets you have breakpoint calls in your Rails code and then you run the breakpointer script which attaches to an irb (interactive Ruby; think perl -de 0) session which interacts with the Rails app via DRb calls.)

Use perl -d scriptname.pl. You can can step through the script and then use x %sth to inspect the vars. You can also use V main to view all vars in the main package.

take a look at perlrun and perldebug

First you must have error logs file path in your server. With that you can able to trace the error in the file. Or you can just add the following code to see whether that particular function is working or not:

print "Content-type:text/html\n\n";
print "here";
[download]