You are using Xdebug v3 but keep using Xdebug v2 config parameters. You need to go through Upgrading from Xdebug 2 to 3 Guide and adjust your settings. Xdebug v3 uses different config params than Xdebug v2 (your phpinfo() output tells you exactly that on your screenshot). 5 out of 6 “xdebug.” params from your … Read more
after struggling with this issue for several hours today, I decided to manually cat all informations inside one single .ini file, and started eclipse with eclipse -clean. something like the following script should do the trick: #!/bin/bash mkdir /etc/php5/cli_eclipse cat /etc/php5/cli/php.ini /etc/php5/conf.d/* > /etc/php5/cli_eclipse/php.ini (you could obviously check if the dir is already existing etc. … Read more
It looks like there is something wrong with the path to the file containing the breakpoint. <- breakpoint_set -i 452 -t line -s enabled -f file:///http:/development.xxx.de/users/itsame/index.php -n 15 -> I’ve had a similar problem with Eclipse. Only my breakpoints in the index file were accepted and breakpoints in other files—that were included in the index—were … Read more
The server running PHP (and XDebug) needs to be able to connect to your workstation/desktop. So you’ll need the server set up accordingly by either telling it to connect to a specific IP-address (xdebug.remote_host) or to automatically “connect back” (xdebug.remote_connect_back). The latter has some security implications, though. These are outlined in the manual.
In my case this was caused by having xdebug.remote_autostart = 1 set in php.ini. That causes xdebug to try to connect to remote debugger on every request. I had some PHP handled styles, auto_preppend_file and other PHP files in the request and for each of them it waited approximately 2secs, which added up to sth. … Read more
Docker on Linux allows Xdebug to automatically connect back to the host system so you can just set xdebug.remote_connect_back=1 and leave out the xdebug.remote_host in your xdebug.ini.
I’ve found a more modern and easier solution partially based on CrasyCoder’s post. The steps you need to do are the following: If your brand new php installation doesn’t contain php.ini, rename the php.ini-development to php.ini Install xdebug with help of the wizard: http://xdebug.org/wizard.php Follow its recommendations literally. Put in your php.ini the string: xdebug.remote_enable=1 … Read more
There are some similar issues reported http://bugs.xdebug.org/view.php?id=900 https://bugs.php.net/bug.php?id=60778 One way to get rid of this messages is to add unset($stmt); after closing the statement and before the breakpoint. If this does not help, you should also add unset($connection); after closing the connection as mentioned by @Martin in the comments. This does not solve the problem … Read more
You are using PhpStorm 2018.1.x with Xdebug 2.7. Either upgrade PhpStorm to the latest stable 2018.3.x or downgrade Xdebug to 2.6.x The problem is in recently changed XML namespace in Xdebug protocol, as of Xdebug 2.7 (https instead of http). It’s fixed/supported since PhpStorm 2018.3 (see WI-43622).
I found the problem was Xdebug in xampp\php\php.ini. Here’re the results of trying many solutions found around the web: Run XAMPP as adminisrator and restart server: 3617 ms In xampp/apache/conf/httpd.conf, replace localhost with 127.0.0.1 and restart server: 3639 ms In Windows/System32/drivers/etc/hosts, add “127.0.0.1 127.0.0.1” & “127.0.0.1 localhost” and restart Windows: 3960 ms In Windows/System32/drivers/etc/hosts, un-comment … Read more