I think the safest way is to subclass whatever registry you're using ... but maybe you can borrow from ModPerl::RegistryCooker
###################################################################### +### # func: error_check # dflt: error_check # desc: checks $@ for errors # args: $self - registry blessed object # rtrn: Apache2::Const::SERVER_ERROR if $@ is set, Apache2::Const::OK +otherwise ###################################################################### +### sub error_check { my $self = shift; # ModPerl::Util::exit() throws an exception object whose rc is # ModPerl::EXIT # (see modperl_perl_exit() and modperl_errsv() C functions) if ($@ && !(ref $@ eq 'APR::Error' && $@ == ModPerl::EXIT)) { $self->log_error($@); return Apache2::Const::SERVER_ERROR; } return Apache2::Const::OK; }
In reply to Re: grabbing un-handled exceptions via modperl2
by Anonymous Monk
in thread grabbing un-handled exceptions via modperl2
by mmlenz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |