php-src/sapi/phpdbg/tests/exceptions_001.phpt
Tim Düsterhus 08b2ab22f4
Include the source location in Closure names (#13550)
* Include the source location in Closure names

This change makes stack traces involving Closures, especially multiple
different Closures, much more useful, because it's more easily visible *which*
closure was called for a given stack frame.

The implementation is similar to that of anonymous classes which already
include the file name and line number within their generated classname.

* Update scripts/dev/bless_tests.php for closure naming

* Adjust existing tests for closure naming

* Adjust tests for closure naming that were not caught locally

* Drop the namespace from closure names

This is redundant with the included filename.

* Include filename and line number as separate keys in Closure debug info

* Fix test

* Fix test

* Include the surrounding class and function name in closure names

* Fix test

* Relax test expecations

* Fix tests after merge

* NEWS / UPGRADING
2024-04-12 18:21:13 +02:00

48 lines
856 B
PHP

--TEST--
Properly handle exceptions going to be uncaught
--PHPDBG--
r
t
ev 1 + 2
c
q
--EXPECTF--
[Successful compilation of %s]
prompt> handle first
[Uncaught Error in %s on line 16: Call to undefined function foo()]
>00016: foo(); // Error
00017: } catch (\Exception $e) {
00018: var_dump($e);
prompt> frame #0: {closure:%s:%d}() at %s:16
frame #1: {main} at %s:22
prompt> 3
prompt> [Uncaught Error in %s on line 16]
Error: Call to undefined function foo() in %s:16
Stack trace:
#0 %s(22): {closure:%s:%d}()
#1 {main}
[Script ended normally]
prompt>
--FILE--
<?php
(function() {
try {
foo(); // Error
} catch (\Exception $e) {
var_dump($e);
} finally {
print "handle first\n";
return "ok";
}
})();
(function() {
try {
foo(); // Error
} catch (\Exception $e) {
var_dump($e);
} catch (\ParseError $e) {
var_dump($e);
}
})();