Bug#703000: apache-preforks, &, modperl, segfaults

Salvatore Bonaccorso carnil at debian.org
Thu Mar 14 13:16:00 UTC 2013


Hi

On Thu, Mar 14, 2013 at 05:03:21PM +0400, Dmitry E. Oboukhov wrote:
> >> I downgraded mod-perl, 2.0.7-1 crashes, too (the same backtrace)
> >> 
> >> Then I downgraded apache to 2.2.22-12 and 2.2.22-12 + modperl 2.0.7-1
> >> don't crash. Also apache 2.2.22-12 and modperl 2.0.7-2 don't crash,
> >> too.
> >> 
> >> But backtrace points to mod-perl, so I doubt to reassign the
> >> bugreport.
> 
> > As an additional data point, I am happily running apache2/mod_perl2
> > from unstable/amd64 with no issues.
> 
> > apache2 is 2.2.22-13 and libapache2-mod-perl2 is 2.0.7-3, which
> > basically is the same as Dmitry's environment.
> 
> Now I've upgraded apache2 to 2.2.22-13 (again) and upgraded mod-perl
> to 2.0.7-3 and I can't reproduce the bug.
> So may be it is worth to rebuild mod-perl 2.0.7-2 with new apache
> or to push 2.0.7-3 to testing?

This is the plan, since 2.0.7-3 fixes a FTBFS with the recent perl
update needed. But there is still a wait period of 4 days left (it was
already unblocked by the Release Team) and there is a build failure
for s390 on buildds.

But it's still curious what cause the incompatibility...

Regards,
Salvatore



More information about the pkg-perl-maintainers mailing list