![]() ![]() I: Checking header 'HTTP_X_FORWARDED_FOR'. Come along and watch Susi demonstrate how easy it is to set up debugging with PHPstorm and Xdebug. I: Checking remote connect back address. Using the Xdebug PHP extension to debug your applications is not only faster, it’s also more efficient and gives you a deeper insight into the control flows of your application. W: Creating socket for '172.18.0.1:9000', poll success, but error: Operation now in progress (29). ![]() I also have "stop at first line" enabled. The xdebug.log file has the following output after making a request and attempting to pick up a break point. Enable listening to incoming debugging connections Toggle the Start Listen PHP Debug Connections button on the PhpStorm toolbar or status bar so that it changes to. These are basically the same settings that do work in other Ansible/Vagrant based machines that I have running locally (all of them have been suspended while testing ddev). Zend debugger You can also Validate the Configuration of a Debugging Engine in PhpStorm to make sure that the provided configuration parameters are correct. I'm setting my own 20-xdebug.ini file which is 100% accepted and showing correct values when I run phpinfo(). Here are my settings: APIVersion: v1.13.0 I've tried changing ports and did all the steps in this thread How do I get xdebug/step-debugging working with ddev? to no avail. I'm new to ddev, but not new to Ansible, Vagrant, etc, or setting up Xdebug, and I can't for the life of me get step debugging to work with PhpStorm and ddev.
0 Comments
Leave a Reply. |