Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21989 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51583 invoked by uid 1010); 23 Feb 2006 04:29:11 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 51568 invoked from network); 23 Feb 2006 04:29:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Feb 2006 04:29:11 -0000 X-Host-Fingerprint: 64.233.184.193 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.193:28458] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 70/61-36719-51A3DF34 for ; Wed, 22 Feb 2006 23:29:09 -0500 Received: by wproxy.gmail.com with SMTP id 57so1524817wri for ; Wed, 22 Feb 2006 20:29:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=D8tq1U6stey5Ciz2gA21ztOIqSLUmM9hBomapTOKb1oqfC+9Hd40hye+Aln2a9yiCkRcAFY7oRtiAV3O674+puBR40dFHKPPfQk8FpPpl8h13QmctO04E6Tx9ZpEoXclO5bGD4rIu3VoRjWI9M/OnJ6CYh6YYyvL13JW/q0J3mA= Received: by 10.54.82.3 with SMTP id f3mr170343wrb; Wed, 22 Feb 2006 20:29:06 -0800 (PST) Received: by 10.54.77.7 with HTTP; Wed, 22 Feb 2006 20:29:06 -0800 (PST) Message-ID: <4e89b4260602222029s454a0075jbdeadd1ec4b8372b@mail.gmail.com> Date: Wed, 22 Feb 2006 23:29:06 -0500 To: "Ilia Alshanetsky" Cc: "Nuno Lopes" , PHPdev In-Reply-To: <43FB9D99.5070302@prohost.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <005101c6373a$a6ef0170$0100a8c0@pc07653> <43FB9D99.5070302@prohost.org> Subject: Re: [PHP-DEV] recover from a segfault From: kingwez@gmail.com ("Wez Furlong") If we do do this, please make it optional; it's bad form when a module or a library unilaterally changes a process-wide option or setting and impacts a system that has already been tuned; the sysadmin may already have set up appropriate limits. --Wez. On 2/21/06, Ilia Alshanetsky wrote: > Nuno Lopes wrote: > > PCRE can consume a lot of stack, because of backtracking (thus > > segfaulting PHP). Yesterday I've discovered that when using the > > setrlimit() function, most segfaults can be avoided > > (http://mega.ist.utl.pt/~ncpl/php_pcre_stack_limits.txt) :) > > This sounds like an interesting idea, I think we need to consider it > doing for PHP in general rather then jut when PCRE is being used. The > only thing is that rather then setting the stack to infinity, perhaps a > small value can be used ;-)