xdebug.org | Xdebug Website - | Web Site library

If you are using vscode IDE, than check your port in launch.json file. keep it 9000 and restart your vscode.

you can copy launch.json file from here.

Congratulations! You have found a bug, I think.

Would you please be so kind to report it to the Xdebug development team at https://bugs.xdebug.org ? Just copying and pasting the whole information from this post their issue tracker will likely be enough for them to fix this (if it turns out to be a real bug).

I have plans to make the dbgpClient that you mention, remember breakpoints that have been set through it. I haven't had the time to implement that yet.

For now, you can use the xdebug_break() function to interrupt the execution flow, and make the debugger pause.

While I can't exactly say what is the problem, I suggest making these changes:

• Make sure the Run menu has this menu item: .
• Remove the Filter debug connection by IDE key configuration. The IDE key is somewhat useful if you have multiple websites that need to go to different environments, but I'm guessing that's not an issue for you.
• Enable Break at first line in PHP scripts.

There might be a couple of additional ideas in the troubleshooting section here.

Finally with the help of @LazyOne I could figure this out.

The root cause of the problem was that due to a macOS update my terminal in VSCODE was replaced with a new terminal, zsh.

This terminal did not have the right php path/version configured, therefore when I ran the artisan commands from the command line, I run it with the default php version without Xdebug installed.

When I changed the path to the php version installed under my MAMP package, it just worked. To make this more convenient, I added an alias to the zsh configuration file pointing to the right php version.

Is there anyway that I prevent xdebug to listening?

No, because it is not Xdebug that is listening. It is Xdebug that makes a connection to PhpStorm, which can be listening for incoming debugging connections.

It is possible that for some reason, Xdebug still attempts to make a connection to the IDE, even if it is not listening. There is normally a 200ms timeout on the Xdebug side when connecting, but I have seen some network setups thwarting that.

In order to find out what, and if, Xdebug is still doing something, make a log file, by changing your xdebug.ini to include the following, and then restart Apache:

Check the log. Check if xdebug connects, if it tries to connect to correct ip. In my case it was trying to to connect to wrong ip. So needed to change this config to this value:

xdebug.remote_host=192.168.31.26

Next thing - PhpStorm started writing

Cannot parse server name for external Xdebug connection. To fix it create environment variable PHP_IDE_CONFIG on the remote server. Windows: set PHP_IDE_CONFIG="serverName=SomeName" Linux / Mac OS X: export PHP_IDE_CONFIG="serverName=SomeName".

So got in docker container and run the export. ServerName has to be same as Name field in PhpStorm config

There are some changes between PHP 7.4 and 8.0, which change the behaviour of error checking for internal eval statements, which Xdebug uses when an IDE sets a watch.

If I base64 decode your (or rather the IDE's) eval statement (eval -i 43 -- KFxnZXRfb3B0aW9uKHNlbGY6OiRTRVRUSU5HU19OQU1FKQ==), it says:

I have finally figured out why the debugger did not work: I launched the debug session inside the container (I connected to it through the Remote - Containers VS Code extension) and not from the Docker host. So, in this case, the correct value for xdebug.client_host is localhost, since both the Xdebug client and the server are on the same host.

To make it work with xdebug.client_host=host.docker.internal, I had set up a Docker volume and I started the debugger directly on Windows, without connecting to the container from inside VS Code. In this case I also had to add a path mapping in the launch.json file, which maps the Docker volume's path to the workspace folder.