Return-Path: Delivered-To: apmail-perl-embperl-archive@www.apache.org Received: (qmail 70996 invoked from network); 17 Mar 2006 20:10:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Mar 2006 20:10:06 -0000 Received: (qmail 97467 invoked by uid 500); 17 Mar 2006 20:10:04 -0000 Delivered-To: apmail-perl-embperl-archive@perl.apache.org Received: (qmail 97366 invoked by uid 500); 17 Mar 2006 20:10:03 -0000 Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list embperl@perl.apache.org Delivered-To: moderator for embperl@perl.apache.org Received: (qmail 72282 invoked by uid 99); 17 Mar 2006 17:13:47 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Message-ID: <20060317171323.51258.qmail@web34006.mail.mud.yahoo.com> Date: Fri, 17 Mar 2006 09:13:23 -0800 (PST) From: BeeThere Admin Reply-To: BeeThere Admin Subject: Re: Intermittent Segfaults To: embperl@perl.apache.org In-Reply-To: <20060316042852.AA1003D209B@lnx1.i.ecos.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks, I have continued testing, and I can confidently say that the problem is definitely not an out-of-memory issue. The new dev version you sent is segfaulting about once for every 100 page requests in dev now, with no load except me clicking around, on a machine with 2G total RAM and plenty of free memory. The segfaults have occurred during pretty much every type of page request, and also not occurred on those same requests. Hitting refresh will always result in the page being correctly sent, with not segfault, on at most a couple pushes. Did you get the back-traces I sent? I sent them to your personal account, but I realized that you may check the list more. Every back-trace points to "EMBPERL2_Node_appendChild .... at epdom.c:2835" as the point of segfaulting. The only Embperl tags I ever use are the PerlBlock '[* *], [+ +], [- -]' tags. Is there someway I can bypass this 'epdom' code all together? (I don't see any reason for dom-parsing) This is pretty scary. Thanks, -Carl ----- Original Message ---- From: Gerald Richter To: BeeThere Admin ; embperl@perl.apache.org Sent: Wednesday, March 15, 2006 11:28:50 PM Subject: RE: Intermittent Segfaults > > I noticed segfaults in my error logs a couple days ago. I am > getting 1 for about every 1K page views. I am able to > reproduce it now, but still can't make any sense of it. I'm > sending a backtrace, and my environment. > I will send you my current development version per private mail, because it contains some more checks for out of memory conditions. Please install it with perl Makefile.pl debug make make install This will give additional informations in the backtrace, in case the the segfault happens again. If you still get the segfault, please send me the backtrace again Gerald ** Virus checked by BB-5000 Mailfilter ** --------------------------------------------------------------------- To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org For additional commands, e-mail: embperl-help@perl.apache.org