Re: Is adding print lines the only way to go to find computational error in a scrpt?

If your code doesn't crash at shell, but causes a 500 error in browser, use this at the top of your script:

use CGI::Carp qw(fatalsToBrowser);
[download]

It doesn't catch everything though.

Comment on Re: Is adding print lines the only way to go to find computational error in a scrpt? Download Code

Replies are listed 'Best First'.
Re: Answer: Is adding print lines the only way to go to find computational error in a scrpt? by idle (Friar) on Feb 02, 2006 at 08:54 UTC
One more way, adding at the top of script: `BEGIN {open (STDERR, ">>/path/error.log")}`	[reply] [d/l]