0001155: Local variables are not shown when execution break in error_handler

ID	Project	Category	View Status	Date Submitted	Last Update
0001155	Xdebug	Step Debugging	public	2015-05-28 17:01	2023-11-30 14:50

Reporter	FlyLo	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	resolved	Resolution	fixed
Platform	PHP 5.6.3	OS	Windows 7 64bit
Product Version	2.3.2
Target Version	3.3dev	Fixed in Version	3.3.0

Summary	0001155: Local variables are not shown when execution break in error_handler
Description	Hello, I have tested this only with PHPstorm as the client. With the attached sample code, when breaking the execution inside the error_handler, there are no local variables available for inspection inside the method that triggered the PHP notice/warning. In this case variable $a from method Test->a() is not displayed in any stackframe.
Steps To Reproduce	Please check the screenshot attached. The breakpoint was set on line 4.
Additional Information	Variable $a should be available for inspection
Tags	No tags attached.

Operating System	Windows 7 64bit
PHP Version	5.6.0-5.6.4

derick 2015-05-29 12:44 administrator ~0003093	I can confirm this - no clue as to why yet though. As a note to myself, I am using the following DBGP commands: step_into -i 1 breakpoint_set -i 2 -t line -n 4 run -i 3 context_get -i 4 -d 2 property_get -i 5 -d 2 -n $a

FlyLo 2015-05-29 13:19 reporter ~0003094	Ok, thanks for confirming it. I wasn't sure if it was from XDebug itself or some PHPstorm bug or misconfiguration. I would be happy to help as much as I can, although not sure how, except by testing it further whenever is necessary. And thank you for this awesome tool.

derick 2021-03-17 09:27 administrator ~0005747	Is this issue still relevant to you?

FlyLo 2021-03-19 09:34 reporter ~0005801	Tested with php 8.0.3 NTS + xdebug 3.0.3, and the issue is still here. But it's not relevant to me anymore, as I haven't debugged an error handler since 2015, when I opened this bug report. I'd say it's up to you to decide if the issue is relevant enough to stay open or not. And thank you for an awesome tool!

derick 2022-10-07 12:51 administrator ~0006396	I had another look at this, but it's still not obvious, so I am moving this to 3.3dev again.

derick 2023-11-03 11:16 administrator ~0006667	This got fixed somewhere along the line between Xdebug 3.2.0 and 3.3.0alpha1, so I am closing this.