In the Troubleshooting guide, you will find the description of some common issues and learn how to troubleshoot them. When using Xdebug or Zend Debugger with PhpStorm, some misconfiguration can prevent the debugger from working. To learn how to do it, follow the Create a test configuration for a specific target procedure. Set up a remote PHP interpreter as described in Configure remote PHP interpreters.īesides running an entire application, you may want to run a PHPUnit or Behat test that covers a specific class, function or scenario, with the debugging engine attached. Debugging a PHP CLI scriptĭepending on your environment, you can debug your PHP CLI script locally or remotely.įollow the Debug a PHP CLI script procedure. To check for opened inbound ports, you can use or a similar service. Here, host is the IP address of the local machine PhpStorm is running on. To test direct connection, run the telnet host 9000 (for Xdebug) or the telnet host 10137 (for Zend Debugger) command on the remote server and ensure that connection is established. Otherwise, if direct connection cannot be established, follow the Remote debugging via SSH tunnel procedure. If you can establish direct connection between your machine and the remote server, that is, no firewall, router or ISP is blocking the connection from your remote server to the specific port on the local machine, follow the Zero-configuration debugging procedure. The debugging engine is running on a remote environment (for example, a remote server or a virtual machine).įollow the Zero-configuration debugging procedure. The debugging engine and PhpStorm are running on the same machine.
Debugging a PHP web applicationĭepending on your environment, you can debug your PHP Web application locally or remotely. See Zero-configuration debugging for the detailed step-by-step instructions, and Advanced debugging scenarios for more debugging scenarios. Start the debugging session in the browser using the installed browser extension.ĭuring a debugging session, examine the program state: see variable values, evaluate expressions, step through the program, and so on. For details on getting started with Twig and Blade debugging, refer to Debug Twig templates and Debug Blade templates.
Line breakpoints can be set only on executable lines, but not on comments, declarations, or empty lines. Breakpoints can be set in the PHP context inside PHP, HTML, TWIG, BLADE, and files of other types. If you don’t know how to do it, please visit our instructions on Part 1 here. But before we begin, make sure that you have installed and set up Xdebug with PhpStorm. On the PhpStorm toolbar, toggle to start listening for incoming PHP debug connections, or choose Run | Start Listening for PHP Debug Connections from the main menu. In this second part of the series, I’m going to guide you how to start a debugging session, place a breakpoint and track the debugging progress.
#Xdebug phpstorm install
With the debugging engine installed, you can start debugging by following the zero-configuration debugging approach:Ĭhoose and install the browser extension suitable for your browser.
0 kommentar(er)
