From c9f27ee4227268bc74fc54e0e06102317e614804 Mon Sep 17 00:00:00 2001
From: Nikita Popov <nikic@php.net>
Date: Fri, 15 May 2015 21:04:07 +0200
Subject: Display EngineExceptions like ordinary exceptions

TypeException stays as-is for now because it uses messages that are
incompatible with the way exception messages are displayed.

closure_038.phpt and a few others now show that we're generating
too many exceptions for compound operations on undefined properties
-- this needs to be fixed in a followup.
---
 Zend/tests/bug52484_2.phpt | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

(limited to 'Zend/tests/bug52484_2.phpt')

diff --git a/Zend/tests/bug52484_2.phpt b/Zend/tests/bug52484_2.phpt
index 1639c81029..3ffb2af3e9 100644
--- a/Zend/tests/bug52484_2.phpt
+++ b/Zend/tests/bug52484_2.phpt
@@ -16,4 +16,8 @@ $a->$prop = 2;
 
 ?>
 --EXPECTF--
-Fatal error: Cannot access empty property in %s on line %d
+Fatal error: Uncaught exception 'EngineException' with message 'Cannot access empty property' in %s:%d
+Stack trace:
+#0 %s(%d): A->__set('', 2)
+#1 {main}
+  thrown in %s on line %d
-- 
cgit v1.2.1