Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re: Troubleshooting Perl CGI scripts

by bradcathey (Prior)
on Aug 06, 2004 at 04:04 UTC ( #380446=note: print w/replies, xml ) Need Help??


in reply to Troubleshooting Perl CGI scripts

Excellent "tutorial!" I'm racking my brain and the only thing I can add is to use Data::Dumper. And though it's better to use the Debugger, I resort to print statements for quick traces. Thanks for your hard work.

—Brad
"Don't ever take a fence down until you know the reason it was put up. " G. K. Chesterton

Replies are listed 'Best First'.
Re^2: Troubleshooting Perl CGI scripts
by rinceWind (Monsignor) on Aug 06, 2004 at 13:44 UTC
    You need to add the shebang line to your checklist. Apache (for one) will refuse to run a script without a valid shebang line. It probably belongs next to "What are the scripts permissions?".

    On the subject of shebang lines, Devel::ptkdb is worth a mention for debugging. You can get this invoked directly from the shebang line

    #!/usr/local/bin/perl -d:ptkdb
    On a windows box, a ptkdb window will pop up when you access the url. On Unix, if you configure $ENV{DISPLAY} in apache you can get the ptkdb window to pop up in an X window.

    --
    I'm Not Just Another Perl Hacker