View Issue Details

IDProjectCategoryView StatusLast Update
0001155XdebugStep Debuggingpublic2021-03-20 18:18
ReporterFlyLo Assigned Toderick  
PrioritynormalSeverityminorReproducibilityalways
Status acknowledgedResolutionopen 
PlatformPHP 5.6.3OSWindows 7 64bit 
Product Version2.3.2 
Target Version3.2dev 
Summary0001155: Local variables are not shown when execution break in error_handler
DescriptionHello,

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 ReproducePlease check the screenshot attached.

The breakpoint was set on line 4.
Additional InformationVariable $a should be available for inspection
TagsNo tags attached.
Operating SystemWindows 7 64bit
PHP Version5.6.0-5.6.4

Activities

FlyLo

2015-05-28 17:01

reporter  

xdebug_issue.png (57,356 bytes)   
xdebug_issue.png (57,356 bytes)   

FlyLo

2015-05-28 17:02

reporter  

test.php (296 bytes)

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!

Issue History

Date Modified Username Field Change
2015-05-28 17:01 FlyLo New Issue
2015-05-28 17:01 FlyLo File Added: xdebug_issue.png
2015-05-28 17:02 FlyLo File Added: test.php
2015-05-29 12:44 derick Note Added: 0003093
2015-05-29 12:44 derick Assigned To => derick
2015-05-29 12:44 derick Status new => confirmed
2015-05-29 13:19 FlyLo Note Added: 0003094
2015-11-20 23:09 derick Target Version => 2.4.1
2016-07-31 12:36 derick Category Usage problems => Usage problems (Crashes)
2016-07-31 12:38 derick Category Usage problems (Crashes) => Usage problems (Wrong Results)
2016-08-01 20:29 derick Target Version 2.4.1 => 2.4.2
2016-11-12 16:54 derick Target Version 2.4.2 => 2.5.0RC2
2016-11-12 16:55 derick Target Version 2.5.0RC2 => 2.5.0dev
2016-12-04 18:34 derick Target Version 2.5.0dev =>
2020-03-12 16:35 derick Category Usage problems (Wrong Results) => Variable Display
2020-03-12 16:37 derick Category Variable Display => Step Debugging
2021-03-17 09:27 derick Status confirmed => feedback
2021-03-17 09:27 derick Note Added: 0005747
2021-03-19 09:34 FlyLo Note Added: 0005801
2021-03-19 09:34 FlyLo Status feedback => assigned
2021-03-20 18:18 derick Status assigned => acknowledged
2021-03-20 18:18 derick Target Version => 3.2dev