perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cory Omand" <com...@blastwave.org>
Subject Re: Apache 2.2 and libapreq2 2.0.7 segfault
Date Thu, 30 Mar 2006 00:06:46 GMT
Hi,

I am having issues with Apache 2.2 and libapreq2 2.07.  Even very
simple tests which construct new Apache2::Request objects are
resulting in segfaults.  I have the following server setup:

Apache/2.2.0 (Unix) DAV/2 mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.8

This server uses the Apache prefork mpm, under Solaris 10.  I set up
the following simple PerlResponseHandler as an initial test:

-- snip --

package SimpleHandler;

use Apache2::Request;

sub handler {
    my $r = shift;
    my $apr = new Apache2::Request($r);

    print "Hello APR\n";
    return Apache2::Const::OK;
}

1;

-- snip --

When I browse to the location served by this handler, I get a
segmentation fault in mod_apreq2:

-bash# mdb /opt/csw/apache2/sbin/httpd
> ::run -f etc/httpd-rms.conf -X
mdb: stop on SIGSEGV
mdb: target stopped at:
mod_apreq2.so`apreq_handle_apache2+0x10:ld        [%i0 + 0x18c], %l3
mdb: You've got symbols!
Loading modules: [ ld.so.1 libc.so.1 libuutil.so.1 ]
> ::stack
mod_apreq2.so`apreq_handle_apache2+0x10(0, 0, 11400, 26f840, 0, 0)
Apache2.so`XS_APR__Request__Apache2_handle+0x11c(1bfe28, 26f840,
195c10, 136638, 4, fdf93778)
libperl.so.5.8.8`Perl_pp_entersub+0x6d0(1bfe28, b33e0, 20, 26f840,
239e10, 26eb18)
libperl.so.5.8.8`Perl_runops_standard+0xc(1bfe28, fe315da0, 0,
fe30d440, fef82000, 239e10)
libperl.so.5.8.8`Perl_call_sv+0x6f8(155f18, 0, 195c10, fe3ad954, 268efc, 0)
mod_perl.so`modperl_callback+0x2c0(1bfe28, 1c7060, 275600, 275638,
82d10, 13d220)
mod_perl.so`modperl_callback_run_handlers+0x548(fe504e5c, 0, 1,
1014f8, fe51fcf0, 0)
mod_perl.so`modperl_callback_per_dir+0x24(6, 275638, 1, 279cc0, 2010, 200c)
mod_perl.so`modperl_response_handler_run+0x18(275638, 0, 153e20,
26961c, 600d, 275638)
mod_perl.so`modperl_response_handler_cgi+0x170(275638, 2, 68, 1a,
fe51f44c, 1ae4)
ap_run_handler+0x40(275638, 101840, 101840, 753d8, 10186c, 1)
ap_invoke_handler+0xd8(275638, 82d10, 275638, 0, 0, 0)
ap_process_request+0x54(275638, 72c00, 4, 275638, 0, 0)
0x4470c(13e2e0, 275638, fffffffe, 1, 1000, 72f30)
ap_run_process_connection+0x40(13e2e0, 101bd8, 101bd8, 75bf4, 101c04, 1)
0x4b7e4(76000, ffbffbb8, 7f3f8, 7310c, 2, 2735f8)
0x4b8cc(82d10, 0, 1, ffffffff, 73000, 1)
ap_mpm_run+0x1c0(81030, 73000, 82d10, 100, 730f4, 75c54)
main+0x990(27558, 72c00, 71ef8, 0, 57800, 71ee8)
_start+0x108(0, 0, 0, 0, 0, 0)
>

I have also tried similar tests with Apache2::Cookie, and see
identical segfaults (and stack traces) to the above.  Any assistance
appreciated.

Regards,
Cory.

Mime
View raw message