php-src/Zend/tests/bug64821.2.phpt

--TEST--
Bug #64821 Custom Exceptions crash when internal properties overridden (variation 2)
--FILE--
<?php

class a extends exception {
	public function __construct() {
		$this->line = array();
	}
}

throw new a;

?>
--EXPECTF--
Fatal error: Uncaught a in %s:0
Stack trace:
#0 {main}
  thrown in %s on line %d
Fixed bug #64821 Custom Exceptions crash when internal properties overridden If user inherits Exception and overrides the properties to arbitrary data types, or simply doesn't run parent::__construct(), here we go. Just convert everything to the appropriate data type, like Exception::__toString() does. 2013-05-12 12:00:32 +00:00			`--TEST--`
			`Bug #64821 Custom Exceptions crash when internal properties overridden (variation 2)`
			`--FILE--`
			`<?php`

			`class a extends exception {`
			`public function __construct() {`
			`$this->line = array();`
			`}`
			`}`

			`throw new a;`

			`?>`
			`--EXPECTF--`
Tweak uncaught exception message display This implements a reduced variant of #1226 with just the following change: -Fatal error: Uncaught exception 'EngineException' with message 'Call to private method foo::bar() from context ''' in %s:%d +Fatal error: Uncaught EngineException: Call to private method foo::bar() from context '' in %s:%d The '' wrapper around messages is very weird if the exception message itself contains ''. Futhermore having the message wrapped in '' doesn't work for the "and defined" suffix of TypeExceptions. 2015-05-17 16:35:18 +00:00			`Fatal error: Uncaught a in %s:0`
Fixed bug #64821 Custom Exceptions crash when internal properties overridden If user inherits Exception and overrides the properties to arbitrary data types, or simply doesn't run parent::__construct(), here we go. Just convert everything to the appropriate data type, like Exception::__toString() does. 2013-05-12 12:00:32 +00:00			`Stack trace:`
			`#0 {main}`
			`thrown in %s on line %d`