Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13118 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94709 invoked by uid 1010); 3 Oct 2004 13:11:59 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 94599 invoked by uid 1007); 3 Oct 2004 13:11:59 -0000 Message-ID: <20041003131159.94598.qmail@pb1.pair.com> To: internals@lists.php.net Date: Sun, 03 Oct 2004 15:12:15 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: nl, en-us, en MIME-Version: 1.0 References: <20041003092545.47146.qmail@pb1.pair.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 213.46.64.114 Subject: Re: [PHP-DEV] PHP (anti) crash policy? From: OlafvdSpek@GMail.Com (Olaf van der Spek) Derick Rethans wrote: > On Sun, 3 Oct 2004, Olaf van der Spek wrote: > >>What is the PHP policy regaring crashes and fatal errors? >>Are scripts allowed to cause a crash or fatal error of Apache/PHP itself? > > Only on a stack overflow, as in: Are there any plans to fix/improve this situation? Isn't it possible to check stack size left before allocating a new stack frame? > > function a() { a(); } > a(); > > Derick >