Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25638 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3408 invoked by uid 1010); 12 Sep 2006 19:01:10 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 3393 invoked from network); 12 Sep 2006 19:01:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2006 19:01:09 -0000 Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 80.74.107.235 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from [80.74.107.235] ([80.74.107.235:53501] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7F/DB-02095-2F307054 for ; Tue, 12 Sep 2006 15:01:09 -0400 Received: (qmail 23204 invoked from network); 12 Sep 2006 18:59:48 -0000 Received: from office.zend.office (HELO ?192.168.61.128?) (192.168.16.109) by internal.zend.office with SMTP; 12 Sep 2006 18:59:48 -0000 Message-ID: <450703E9.3040106@zend.com> Date: Tue, 12 Sep 2006 12:00:57 -0700 Organization: Zend Technologies User-Agent: Thunderbird 1.5.0.5 (X11/20060725) MIME-Version: 1.0 To: Ralph Schindler CC: internals References: <4506FF9D.4030903@smashlabs.com> In-Reply-To: <4506FF9D.4030903@smashlabs.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Acceptable Seg Faults? From: stas@zend.com (Stanislav Malyshev) > > I assume this is b/c its recursively diving into Class function/method > calls and we are filling memory.. Is this detectable? Should I file a > bug report or is this known? Ideally it would be nice to see a fatal > error thrown, if this is indeed detectable. So far nobody had proposed a solution for endless loop problem that would satisfy these conditions: 1. No false positives (i.e. good code always works) 2. No slowdown for execution 3. Works with any stack size Thus, this problem remains unsloved. -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/