On Tuesday, Sep 17, 2002, at 17:56 Europe/London, Jason Adams wrote: > hi > > On the test machine I was playing with the last segfault on, I still > have one minor segfault instance. I don't think it's related the > pervious problem. It seems to occur at rate of about one in a > thousand, so I'm content to ignore it for the time being. > > The segfault itself occurs in "Perl_pp_leavesub". I have a near > useless gdb log if anyone is interested. > > The backtrace is > #0 0x403635bf in Perl_pp_leavesub () from /usr/lib/libperl.so.5.6 > #1 0x4035e411 in Perl_runops_standard () from /usr/lib/libperl.so.5.6 > #2 0x40316b2c in perl_call_sv () from /usr/lib/libperl.so.5.6 > #3 0x4031689e in perl_call_sv () from /usr/lib/libperl.so.5.6 > #4 0x401efa9e in perl_call_handler (sv=0x80e2efc, r=0x82aefc4, > args=0x0) at mod_perl.c:1658 > #5 0x401ef30c in perl_run_stacked_handlers (hook=0x4020b619 > "PerlHandler", r=0x82aefc4, handlers=0x827e5b4) at mod_perl.c:1371 > #6 0x401edbcf in perl_handler (r=0x82aefc4) at mod_perl.c:897 > #7 0x08052b64 in ap_invoke_handler () > #8 0x0806240c in process_request_internal () > #9 0x08062468 in ap_process_request () > #10 0x0805bc4b in child_main () > #11 0x0805bddc in make_child () > #12 0x0805bef9 in startup_children () > #13 0x0805c3d5 in standalone_main () > #14 0x0805cadd in main ()
Might go away by switching to SetHandler axkit instead of PerlHandler AxKit. Matt. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
