> { name => 'CASServerName',
> errmsg => 'Name of the CAS server',
> args_how => 'TAKE1',
> req_override => 'OR_AUTHCFG', }
>
> ---- quote ----
> (gdb) bt
> #0 0x0807d151 in perl_perl_create_cfg (sv=0x888fdcc, pclass=0x816fcc4,
> parms=0xbffffa10, type=0x80ed6c9 "SERVER_CREATE") at perl_config.c:898
sorry to jump into the conversation late, but this strikes me as odd. in
tracing back the code that should be DIR_CREATE and not SERVER_CREATE,
especially if you are defining an OR_AUTHCFG directive for use in a
.htaccess file. are you defining 'sub SERVER_CREATE' in your .pm file? you
shouldn't need one, so if you have that and SERVER_MERGE defined try taking
them out or moving them to DIR_CREATE/MERGE instead.
historically, some people have reported that directive handlers in mp1 cause
segfaults at random, similar to the way you describe in that your handler
runs but the request later segfaults. I have not personally witnessed this
but it has been reported :) there are also a few modules that use .htaccess
files with directive handlers, such as Apache::Dispatch and
Apache::Template, but I can't recall any reported problems there that
stemmed specifically from .htaccess files.
at this point, I think stas has gotten us as far as we can go with gdb (and
much farther than I could have, for sure). what would be _really_ helpful
at this point would be to reduce your code as much as possible using
Apache-Test to recreate the issue, the tar it up. see
http://perl.apache.org/~geoff/bug-reporting-skeleton-mp1.tar.gz
for a skeleton and the README for directions. if you can reproduce it there
it will get us much closer to tackling the issue at hand. if it's not
reproducable once you reduce the code to just the mechanics of your hander,
then it must be your code ;)
HTH
--Geoff
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
