Local variables not added to watch window when created dynamicall
Hi,
So I have the following in a function: extract(Array("a"=>1));
I would expect the variable $a to then show up in the watch window, but it does not.
I added: /** @var $a string */
but that did not seem to help.
I looked through everything I could find in the forum and help files, and nothing seems to address my problem. Any help would be appreciated.
请先登录再写评论。
Oh, and related to the same problem, these variables show as errors in the IDE when used as they have "not been initialized".
Hi there,
1) What's your PHP & xdebug versions?
2) Please provide complete code sample (complete standalone file) to reproduce the issue
3) If you can repetitively reproduce it -- please collect xdebug log -- https://xdebug.org/docs/all_settings#remote_log
Here is my test: PhpStorm 2016.3.2 on Windows 10; PHP 7.0.16 nts; xdebug 2.5.0; debugging in CLI ("PHP Script" type of Debug Configuration) this simple script:
Works just fine here -- $a variable appears in variables view straight after executing that line.
>I added: /** @var $a string */
> but that did not seem to help.
It should not help -- PHP/xdebug (those that provide this actual info about variables to IDE) do not interpret PHPDoc comments.
Thanks for the quick answer!
Your sample works when in the global scope, but not in a function.
Tested in php v5.6.30 in Windows with the version of xdebug that comes with it (2.5.0.3).
And then I also compiled the latest version of xdebug from source in the latest version of php7 (7.1.2). It doesn't exactly have a version number, but I think it is considered 2.5.1 branch. Needed to to fix that bug I mentioned in my other thread regarding control statements with out braces. Happy to report it fixed that problem :-) -- I'm honestly shocked though that I couldn't find anyone else in your forums mentioning they had that problem.
Are there no annotations or whatnot that can force the variables into the IDE scope without actually manually declaring them?
This must be purely xdebug/PHP issue. Please report it there.
You may enable & collect xdebug log (xdebug.remote_log) and see what is happening there yourself.
Below is mine -- 2 sessions:
P.S.
In case if you do not know what to look at -- look for response for "context_get" command with "-c 0"
For 1st session:
<- context_get -i 11 -d 0 -c 0 (breakpoint at extract(...) line is hit)
<- context_get -i 17 -d 0 -c 0 (that line was executed -- now on $b = 22; line)
<- context_get -i 23 -d 0 -c 0 ($b now has value -- about to execute $c = 12; line)
>Are there no annotations or whatnot that can force the variables into the IDE scope without actually manually declaring them?
For IDE alone -- yes -- you already used it (via PHPDoc: /** @var MyClass $a */ -- for example) -- but it does not affect xdebug in any way.
If you know for sure that such variable exists & need to see its value -- just add it as watch manually (Here on screenshot I'm using separate panels fro Variables and Watches)
>I'm honestly shocked though that I couldn't find anyone else in your forums mentioning they had that problem.
AFAIR there were 1 or 2 posts ... but last time it was like 2 years ago or so (as I remember replying there).
(possibly offtopic .. but a bit related to your other post and this one)
https://youtrack.jetbrains.com/issue/WI-20398#comment=27-599855 ---> https://bugs.xdebug.org/view.php?id=949
https://youtrack.jetbrains.com/issue/WI-30010 (was fixed in xdebug)
You may also look at some of the issue PHP Debug tickets that were closed as "3rd party issue" (different reasons, not just xdebug): https://youtrack.jetbrains.com/issues/WI?q=%23{PHP debug} %23{3rd party issue}
Again, I appreciate the help. I went ahead and submitted the bug to xdebug.
For the stuff about the other post, the links you gave are different issues, but the actual problem has been fixed in yet-unreleased versions.
Out of curiosity, may I ask what your relationship is with jetbrains?