Geoffrey Young wrote:
Please show us the backtrace, Geoff.
I've been staring at them all night but maybe they will make sense to you :)
it's different on prefork and worker.
No, it doesn't :( I expected to see problems in the apr/apache io layers, but
you get it in totally different places.
Jo
>
> Please show us the backtrace, Geoff.
I've been staring at them all night but maybe they will make sense to you :)
it's different on prefork and worker.
prefork:
#0 0x08076165 in ap_get_module_config (cv=0x0, m=0xeb8820) at util_debug.c:105
#1 0x00d692bb in modperl_hook_create_request (r
Geoffrey Young wrote:
hi all
I've traced the 2.1 issue reported on modperl@ (and seen by both philippe
and I) down to this APR change:
http://marc.theaimsgroup.com/?l=apr-cvs&m=108039307912906&w=2
building Apache with --disable-lfs puts everything back to normal.
now, I'm not sure whether the
hi all
I've traced the 2.1 issue reported on modperl@ (and seen by both philippe
and I) down to this APR change:
http://marc.theaimsgroup.com/?l=apr-cvs&m=108039307912906&w=2
building Apache with --disable-lfs puts everything back to normal.
now, I'm not sure whether the problem is with APR,
Kiki wrote:
I couldn't find any references to a possible cause of the segmentation
fault. Does mod_perl 1.99_13 solve this problem?
We are not aware of this problem, Kiki. You need to give us more matter to be
able to understand your problem. You don't have a problem to start the modperl
test sui
I couldn't find any references to a possible cause of the segmentation fault. Does
mod_perl 1.99_13 solve this problem?
Anyway, here's the bug report:
1. Problem Description:
Segmentation fault when starting Apache2 with mod_perl
2. Used Components and their Configuration:
*** mod_perl versio
