On Fri, Sep 4, 2009 at 12:00 PM, James Olsen wrote:
> The trouble is, our code isn't getting invoked at all. Mod_perl (or
> something lower-level like that) is dying complaining that our code
> can't be found on the hits where this happens.
Did you try $SIG{__DIE__}? It's a global setting for tha
Hello Perrin,
Thank you for your response.
PH> You could:
PH> - Make s $SIG{__DIE__} handler
PH> - Wrap your application in an eval {}
PH> The data you want is available from either the standard apache log
PH> formats or perl code in Apache::Status, so there's no need to worry
PH> about writing
On Thu, Sep 3, 2009 at 11:32 AM, James Olsen wrote:
> I would like to know if someone has a patch that will dump out more
> information about the hit, such as the requested URI, any parameters
> that are passed, what perl modules are in memory, the process ID, or
> anything at all that might help.
Hello,
We are running Apache/1.3.37 with mod_perl/1.29. We use the regular
mod_perl API to install custom access, authentication, authorization,
fixup, content, and logging handlers.
Once in a great while we run into random "Undefined subroutine
XX::Clients::YY::ContentHandler::handler called.
