Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:5802
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Sat, 29 Nov 2003 15:39:17 +0100
To: internals@lists.php.net
Message-ID: <20031129143917.GA11269@gjat.josefine.at>
Mail-Followup-To: Markus Fischer <mfischer@gjat.josefine.at>,
	internals@lists.php.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Microsoft Outlook Express 5.50.4807.1700.314
Subject: beta2, deriving from class Extension and calling parent::__toString() segfaults
From: mfischer@gjat.josefine.at (Markus Fischer)

  When trying to derive from class Exception and access the 'string'
  property or call 'parent::__toString' PHP segfaults:

<?php
    class MyException extends Exception {
        function __toString() {
            var_dump($this->string);
        }
    }

    throw new MyException("hmm");
?>

Output:

$ php testException.php
NULL
Segmentation fault

  Or this example:

<?php
    class MyException extends Exception {
        function __toString() {
			parent::__toString();
        }
    }

    throw new MyException("hmm");
?>

Output:

$ php testException.php
Segmentation fault


	The need for this came up when I saw that the reported exception is
	not foramted in the HTML output; it's quite hard next to impossible
	to properly read the stack trace. So my goal was to make my own
	exception and call nl2br() on the string returned from the class.

	Besides the segfaults above, is there a chance we have a nicer HTML
	formatting for reported Exceptions (while still strip those HTML
	tags from it for logging)?

	- Markus