perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <>
Subject Re: modperl_require_module failing silently
Date Tue, 27 May 2003 00:22:05 GMT
Geoffrey Young wrote:
> Stas Bekman wrote:
>> Geoffrey Young wrote:
>>> hi again
>>>   I'm finding it very difficult to resolve module errors without this 
>>> patch.
>> Can't do that "fix", because modperl_handler_resolve calls 
>> modperl_mgv_resolve and handles errors by itself, sending it as a part 
>> of the error, which on the way logs the error. Your patch will cause 
>> the error to be logged twice.
> hmm...
> btw, why does modperl_mgv_resolve accept logfailure as an argument and 
> then ignore it when calling modperl_resolve_module?

true, its use was lost when I've trimmed the magic code to DWIM, that didn't 
always work. I've replaced hardcoded FALSE to require with this flag. See if 
it helps. patch at the bottom.

>> Can you show a simple case where you have this problem with? is it 
>> because modperl_handler_resolve is called before server has been started?
> well, I'm calling modperl_callback directly from XS, specifying a module 
> that hasn't been loaded with PerlModule.  when the module has an error, 
> all I see it the "failed to resolve handler `%s'" line and not $@, which 
> was frustrating.  from the looks of it, this may happen any time a 
> module is loaded without first using PerlModule, since the only time 
> that flag is TRUE is when mod_perl is walking the config, right?
> anyway, I guess the solution is to use PerlModule, and perhaps fix 
> modperl_mgv_resolve to use that passed flag instead of hardcoding the 
> value.
> --Geoff

Currently we have the following usages for modperl_mgv_resolve. Only
modperl_handler_resolve is using false since the error is logged by itself.
However it does logs the failure reason, when resolved at run time. e.g. break 
t/response/TestModperl/ and run t/TEST -v run

What you are not telling me is what kid of callback you are having a problem 
with. modperl_callback returns the status, which eventually should propogate 
to Apache. Can you trace where the error is lost? It should work from XS code, 
no need to use PerlModule. If it doesn't we need to fix it (without breaking 
other code ;)

This is the usage of modperl_mgv_resolve:


      modperl_filter_runtime_add :

         if (!modperl_mgv_resolve(aTHX_ handler, pool, handler->name, TRUE)) {
             Perl_croak(aTHX_ "unable to resolve handler %s\n", handler->name);


      modperl_handler_resolve :

         if (!modperl_mgv_resolve(aTHX_ handler, rp, handler->name, FALSE)) {
             ap_log_error(APLOG_MARK, APLOG_ERR, 0, s,
                          "failed to resolve handler `%s'",
             return HTTP_INTERNAL_SERVER_ERROR;


      modperl_handler_perl_get_handlers :

             if (!modperl_mgv_resolve(aTHX_ handler, p, handler->name, TRUE)) {
                 MP_TRACE_h(MP_FUNC, "failed to resolve handler %s\n",



      modperl_mgv_resolve(aTHX_ handler, p, handler->name, TRUE)

Index: src/modules/perl/modperl_mgv.c
RCS file: /home/cvs/modperl-2.0/src/modules/perl/modperl_mgv.c,v
retrieving revision 1.25
diff -u -r1.25 modperl_mgv.c
--- src/modules/perl/modperl_mgv.c	17 Apr 2003 08:04:47 -0000	1.25
+++ src/modules/perl/modperl_mgv.c	27 May 2003 00:08:04 -0000
@@ -264,7 +264,7 @@
                     "package %s not defined, attempting to load\n", name);

-        if (modperl_require_module(aTHX_ name, FALSE)) {
+        if (modperl_require_module(aTHX_ name, logfailure)) {
              MP_TRACE_h(MP_FUNC, "loaded %s package\n", name);
              if (!(stash = gv_stashpv(name, FALSE))) {
                  MP_TRACE_h(MP_FUNC, "%s package still does not exist\n",
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message