On Thu, May 7, 2009 at 4:41 PM, Brian Hirt <bh...@mobygames.com> wrote: > I just built up a new mod_perl1.30 with apache 1.3.41 and started seeing > segfaults in my logs. I ended up tracking the problem down to > http://svn.apache.org/viewvc?view=rev&revision=555908 > > It looks like a fix was committed almost 2 years ago. > > So my questions are these. Is a 1.31 ever going to be rolled?
1.31 is in the RC stage: http://www.gossamer-threads.com/lists/modperl/modperl/99482?search_string=gozer;#99482 I believe RC8 will be out in the near future. > If not, > should I be running SVN or should I manually patch this particular bug > against 1.30? > > Thanks for the advice, > > Brian > > (gdb) bt > #0 0x00007f881ab96c43 in Perl_av_undef () from /usr/lib/libperl.so.5.10 > #1 0x000000000043eafb in perl_shutdown (s=<value optimized out>, p=<value > optimized out>) at mod_perl.c:284 > #2 0x0000000000474a79 in run_cleanups () > #3 0x0000000000472c61 in ap_clear_pool () > #4 0x0000000000472ce8 in ap_destroy_pool () > #5 0x00000000004831b5 in clean_child_exit () > #6 0x00000000004852c9 in just_die () > #7 0x00000000004852e6 in usr1_handler () > #8 <signal handler called> > #9 0x00007f881a44a897 in semop () from /lib/libc.so.6 > #10 0x00000000004833ba in accept_mutex_on_sysvsem () > #11 0x000000000048673b in child_main () > #12 0x0000000000486e29 in make_child () > #13 0x0000000000487257 in perform_idle_server_maintenance () > #14 0x0000000000487942 in standalone_main () > #15 0x0000000000487f95 in main () > (gdb) > >
