in reply to Tracking down an error in a mod_perl script

You could try use diagnostics, but this is appears to be specific to mod_perl, and diagnostics is only good for perl's internal errors.

Did you have Apache reload your modules after you changed them? Under mod_perl, it won't do it on its own.

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

Note: All code is untested, unless otherwise stated

Replies are listed 'Best First'.
Re: Re: Tracking down an error in a mod_perl script
by jgallagher (Pilgrim) on May 11, 2003 at 20:20 UTC
    use diagnostics; gave me more information about what the error messages mean, but not where they're occurring.

    As far as the modules go, I have it running under Apache::Reload, but I also restarted it a few times for good measure. :-)