Randy Kobes schrieb:
On Thu, 28 Jun 2007, Jens Helweg wrote:
Hi erveryone,
I am using modperl2 with apache2 on win32 (activestate Perl 5.8). I
have my own perl module included in the apache conf.
Whenever I have an error in my module apache does not start and the
only error message I can find is in apache's error.log:
Can't load Perl file: D:/path_to_my_perl_module for server myserver,
exiting...
It doesn't say anything about what is wrong in the code.
Is there a way to get the compilers output from perl, so I can get
details on what is wrong in the code ?
(when I run perl -c mymodule.pm on command line it complains about
missing modules - so that doesn't seem to be an option when using
modperl.)
Thanks in advance,
Jens
One could use eval to require the module, and if there's a
problem, print $@ to the error log. But probably the most
efficient way is to first fix any errors from
"perl -c mymodule.pm".
I thought perl -c mymodule.pm is no option when developing modperl
handler modules because these will only run/build in the apache modperl
environment and not on command line ?
How do the modperl pros find an error in modperl modules when all apache
tells is that it can't load the module instead of priting the complete
error that the perl compiler/parser has with the code.
When I run a perl script from command line, perl will give some details
on what is wrong with my code. This information must be somewhere when
apache/modperl starts and compiles my module ? Mabye there is some sort
of switch to turn it on ?
Sorry I'm new to this whole modperl thing...
Thanks for you response !
Jens
