Help Diagnosing Perl Module Dependencies
August 19, 2006.     Douglas Nerad

I was trolling the MailingList and noticed a very good tip from a certain Peter G (website, Peter, so I can link to you?). He was trying to install a plugin that had certain Perl module dependencies, but maybe because he didn't have access to the server error logs he couldn't figure out which modules were missing.

So he added this line to his blosxom.cgi which then dumped the errors into the web browser, making for easy diagnosis:

use CGI::Carp qw(fatalsToBrowser);
It's an excellent and simple diagnosis tool, and we hope it helps others!

Click the button to

 

Pete wrote
2006/9/10 16:26:35

I've got a website, but it's not up at the moment. Talk about great timing, just after I posted to the list I moved house and have been involved with looking for work since. I wrote up a little bit more detailed howto as well. When I get my life sorted out and hook up some internet access I'll let you know :)
douglas.nerad wrote
2006/9/12 20:24:59
Excellent!
I'm looking forward to it!
Randal L. Schwartz wrote
2006/11/27 16:36:14
beware though
DO NOT leave that line in a production website. The first time your database fails, you'll be spitting out for $J_Random_User precisely what your database parameters are... exactly what the bad guys want to know.