[Catalyst] MOD_PERL environment variable
alan.humphrey at comcast.net
Fri Jan 27 20:45:06 CET 2006
CGI::Cookie expects MOD_PERL_API_VERSION to be set to 2 if you're using
mod_perl2. Otherwise it works with mod_perl, which is wrong.
Put $DB::Single=1; anywhere in your code where you want the debugger to
stop and it'll stop there, even at compile time.
Still trying to figure out why $c->engine->apache is undef.
From: catalyst-bounces at lists.rawmode.org
[mailto:catalyst-bounces at lists.rawmode.org] On Behalf Of Alan Humphrey
Sent: Friday, January 27, 2006 9:53 AM
To: catalyst at lists.rawmode.org
Subject: [Catalyst] MOD_PERL environment variable
What is it about setting MOD_PERL that affects inheritance?
If I set MOD_PERL before running my test script I get the message:
Can't locate object method "new" via package
/usr/pkg/lib/perl5/site_perl/5.8.0/Catalyst.pm line 1776.
If it is unset the runtime error when I run the catalyst test script is:
[Fri Jan 27 09:37:23 2006] [catalyst] [error] Caught exception in engine
"Can't call method "connection" on an undefined value at
/usr/pkg/lib/perl5/site_perl/5.8.0/Catalyst/Engine/Apache.pm line 22."
Line 1776 of Catalyst.pm is
$class->engine( $engine->new );
I can't see where setting MOD_PERL would have this effect.
Related info and question:
- This is a clean install of Catalyst 5.63. I manually deleted all
references to Catalyst on my system and then used CPAN to install
- I'm setting MOD_PERL to mod_perl/2.000001 which is the version of mod_perl
on my system.
- My application uses -Engine=Apache2::MP20 in the use Catalyst line.
- How do folks debug the application setup process? I've been peppering
Catalyst.pm and others with various prints, warns, and dies. I'd really
like to be able to step through the code in the debugger.
Any pointers are greatly appreciated!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalyst