Open rfay opened 1 month ago
Unable to replicate on VSCode. Perhaps we can replace "IDE" with "PHPstorm" in the title and description?
$ ddev xdebug toggle
Building project images...
...
Enabled xdebug
DDEV: 1.23.0
VSCode: 1.89.1
VSCode xdebug.php-debug 1.34.0
The problem happens when you:
OK,
$ ddev xdebug
Enabled xdebug
$ ddev xdebug toggle
Disabled xdebug
$ ddev xdebug
Enabled xdebug
$ ddev xdebug toggle
Disabled xdebug
Thanks for the careful testing. I doubt that this is different between PhpStorm and vscode, but it may very well be different between macOS (where I tested) and Win/WSL2.
In my testing I didn't exercise the website or breakpoints at all. I just ddev xdebug
and then ddev xdebug status
or ddev xdebug toggle
Just tried on Gitpod to remove the OS
variable.
Running ddev xdebug
and then ddev xdebug status
then ddev xdebug toggle
doesn't seem cause any hangs in the Gitpod VScode or it's terminal.
Can anyone replicate it on Gitpod or Codespaces?
Expected Behavior
ddev xdebug status
andddev xdebug toggle
should "just work" no matter what the situation.Actual Behavior
If an IDE is listening on port 9003, and xdebug is enabled, both of these hang.
Steps To Reproduce
ddev xdebug on
ddev xdebug status
orddev xdebug toggle
will hangAnything else?
More detail and ideas in
We can probably safely use
php --version | grep -i xdebug
for this more safely and prevent this problem.It would also be trivial to change to
XDEBUG_MODE=off php -r 'echo ini_get("xdebug.mode");'
, which would work for Xdebug 3, it might not be right for Xdebug 2.