On 29/3/09 15:30, Jozef Kosoru wrote: > Hello, > > I tested my mod_perl application using following combinations recently: > > * Apache/2.2.9 (Debian) mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 > (default Debian Lenny packages, mpm-prefork) > > * Apache/2.2.11 (Unix) mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.0 > (apache, apreq and mod_perl compiled from sources, mpm-prefork) > > and I see a crash of Apache process on each request.
Just to be sure, is that a 32/64 bit platform ? > Here's the backtrace: > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb7ce0ad0 (LWP 11196)] > 0xb7bf2095 in Perl_pp_undef () from /usr/lib/libperl.so.5.10 > (gdb) bt > #0 0xb7bf2095 in Perl_pp_undef () from /usr/lib/libperl.so.5.10 > #1 0xb7bc2dc1 in Perl_runops_standard () from /usr/lib/libperl.so.5.10 > #2 0xb7bbcd38 in Perl_call_sv () from /usr/lib/libperl.so.5.10 > #3 0xb7cb2bfc in modperl_callback (my_perl=0x9ab21a0, handler=0x9639b18, > p=0x9ad4578, > r=0x9ad45b8, s=0x961bfe0, args=0x98a13c0) at modperl_callback.c:101 Hrm, if at all possible, while in gdb, could you dump more information from that frame ? (gdb) info locals Also, I'd love to see as much of the arguments as possible, expecially handler, r and args (gdb) print *handler (gdb) print *r (gdb) print *args Thanks. Also, one thing that always help narrow things down is if you could boil down your application to a small enough test case that you could share it with us. -- Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5 http://gozer.ectoplasm.org/ m/gozer\@(apache|cpan|ectoplasm)\.org/
signature.asc
Description: OpenPGP digital signature
