Re: [mp1] segmentation fault in Apache->server->dir_config()

[prev] [thread] [next] [Date index for 2005/04/27]

Mike Taylor wrote:
> I wonder if anyone has any light to shed on this peculiar problem?

hmm, I guess there still some people using mp1. This is so unfashionable. 
Everybody wears RC5 these days :)

> Last night I rebooted a server that's been running happily for several
> months, changing nothing.  When it came up, all my HTML::Mason-based
> sites no longer worked, with all requests routed through Mason causing
> the child server to seggy-fault with no information in the logs.
[...]
> The bizarre thing is that, as I said, _nothing_ has changed since
> yesterday, when this worked just fine.

Mike, have you by chance upgraded some modules between the last server 
startup and reboot? Remember that mod_perl won't see any changes until 
restarted, so if you did change things you could have known whether they 
have affected mod_perl or not.

> I tried to run httpd under both strace and gdb, but I have not managed
> to get any useful information out of it that way.  I am using Apache
> 1.3.33 with mod_perl 1.29 (the most recent 1.x versions of both, I
> believe) both built from source.

Mike, you need to get the core backtrace. Please check:
'Getting the Backtrace From Core Dumps' at
http://perl.apache.org/docs/1.0/guide/help.html#How_to_Report_Problems
for details. Also an output of 'perl -V' would be helpful.


        -- 
        __________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@xxxxxx.xxx http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com