Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 52439 invoked from network); 8 May 2009 04:37:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 May 2009 04:37:37 -0000 Received: (qmail 25013 invoked by uid 500); 8 May 2009 04:37:35 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 24950 invoked by uid 500); 8 May 2009 04:37:35 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 24942 invoked by uid 99); 8 May 2009 04:37:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 May 2009 04:37:34 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.44.154] (HELO yx-out-1718.google.com) (74.125.44.154) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 May 2009 04:37:25 +0000 Received: by yx-out-1718.google.com with SMTP id 36so648970yxh.40 for ; Thu, 07 May 2009 21:37:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.126.19 with SMTP id y19mr7508866anc.46.1241757424117; Thu, 07 May 2009 21:37:04 -0700 (PDT) In-Reply-To: <5F48FD23-D440-4EB7-8B39-68054E91913E@mobygames.com> References: <5F48FD23-D440-4EB7-8B39-68054E91913E@mobygames.com> Date: Thu, 7 May 2009 21:37:03 -0700 Message-ID: Subject: Re: Segfault in Perl_av_undef From: Fred Moyer To: Brian Hirt Cc: modperl@perl.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Thu, May 7, 2009 at 4:41 PM, Brian Hirt wrote: > I just built up a new mod_perl1.30 with apache 1.3.41 and started seeing > segfaults in my logs. =A0 I ended up tracking the problem down to > http://svn.apache.org/viewvc?view=3Drev&revision=3D555908 > > It looks like a fix was committed almost 2 years ago. > > So my questions are these. =A0 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= =3Dgozer;#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 =A00x00007f881ab96c43 in Perl_av_undef () from /usr/lib/libperl.so.5.1= 0 > #1 =A00x000000000043eafb in perl_shutdown (s=3D, p= =3D optimized out>) at mod_perl.c:284 > #2 =A00x0000000000474a79 in run_cleanups () > #3 =A00x0000000000472c61 in ap_clear_pool () > #4 =A00x0000000000472ce8 in ap_destroy_pool () > #5 =A00x00000000004831b5 in clean_child_exit () > #6 =A00x00000000004852c9 in just_die () > #7 =A00x00000000004852e6 in usr1_handler () > #8 =A0 > #9 =A00x00007f881a44a897 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) > >