I get a peculiar "child pid xxxx exit signal Segmentation fault (11)" in my error_log (and the instance aborts) when I assign a value to the MOD_PERL environment variable. The error comes up randomly approximately 50% of the time. Either of the following pieces of code are sufficient to replicate it:
( $ENV{MOD_PERL} ) = ( $ENV{MOD_PERL} =~ /^(.*)$/ );
or
$ENV{MOD_PERL} = "mod_perl/1.99_12";
In both cases I'm assigning the same value to it that it already contains on entry. In case you're curious, the only reason I'm doing this is as part of my untainting process that makes sure that environment variables contain safe values - although in this case it's probably superfluous. The problem is easily fixed by not doing this...
Just thought I'd bring this up in case it's a bug that someone wants to fix. The problem didn't happen with mp1.
Further details: mod_perl-1.99_12-2 httpd-2.0.50-1.0
1) Please upgrade to 1.99_16
2) if the problem persists please submit a proper bug report as explained here: http://perl.apache.org/bugs/
3) Thank you ;)
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- 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
