Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25637
Return-Path: <johannes@schlueters.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 681 invoked by uid 1010); 12 Sep 2006 18:44:46 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 666 invoked from network); 12 Sep 2006 18:44:46 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 12 Sep 2006 18:44:46 -0000
Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain schlueters.de from 212.227.48.61 cause and error)
X-PHP-List-Original-Sender: johannes@schlueters.de
X-Host-Fingerprint: 212.227.48.61 mayflowerholding.com Linux 2.5 (sometimes 2.4) (4)
Received: from [212.227.48.61] ([212.227.48.61:58272] helo=s15175637.rootmaster.info)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 71/7B-02095-C1007054 for <internals@lists.php.net>; Tue, 12 Sep 2006 14:44:46 -0400
Received: (qmail 12385 invoked by uid 2520); 12 Sep 2006 20:44:41 +0200
Received: from 62.245.160.17 by s15175637 (envelope-from <johannes@schlueters.de>, uid 2020) with qmail-scanner-1.25st 
 (uvscan: v4.4.00/v4848. spamassassin: 3.1.4. perlscan: 1.25st.  
 Clear:RC:0(62.245.160.17):SA:0(2.2/5.0):. 
 Processed in 2.138389 secs); 12 Sep 2006 18:44:41 -0000
X-Spam-Status: No, hits=2.2 required=5.0
X-Spam-Level: ++
Received: from ppp-62-245-160-17.dynamic.mnet-online.de (HELO ?192.168.1.104?) (62.245.160.17)
  by mayflowerholding.com with SMTP; 12 Sep 2006 20:44:39 +0200
Message-ID: <4506FFF6.7070807@schlueters.de>
Date: Tue, 12 Sep 2006 20:44:06 +0200
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Ralph Schindler <ralph@smashlabs.com>
CC: internals <internals@lists.php.net>
References: <4506FF9D.4030903@smashlabs.com>
In-Reply-To: <4506FF9D.4030903@smashlabs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Acceptable Seg Faults?
From: johannes@schlueters.de (Johannes Schlueter)

Yes, this is expected.

Ralph Schindler wrote:
> The following script produces a seg fault:
>
> <?
>
> $class = new MyClass();
>
> class MyClass
> {
>
>     public function __construct()
>     {
>         $this->_start();
>     }
>
>
>     public function _start()
>     {
>
>         $this->_myCall();
>
>     }
>
>     public function _myCall()
>     {
>         $this->_start();
>     }
>
> }
>
>
>
> 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.
>
> PHP 5.1.6 / Linux 2.6 / Apache 2
> [notice] child pid 6688 exit signal Segmentation fault (11)
>
>
> -Ralph
>