Long ago, in the node (421127), titled, Where to put long BEGIN blocks used by many programs..., I introduced an error handler that can trap perl compilation errors and redirect them to either the browser or another location (based on a cookie value 'debug').
It's worked great for me, but recently, I've found that certain kinds of errors are not caught, and the browser simply reports the standard Error 500 message. Oddly, the http log doesn't get the output either.
The case that works is if I have any one of a garden variety of syntax errors, much like the following:
print "hello world.;
However, the following error fails to produce any output to the browser, or anywhere else:
foo bar
Clearly, this isn't code at all, but it demonstrates the point I'm trying to make--perl generates an error, but the Carp interface isn't catching it. Why would the code referenced in the above article handle the first case fine, but not the second?
(note that I am up to date with my Carp package.)
In reply to Inconsistent results from CGI::Carp handler by argv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |