Since the debugger runs on a remote machine, starting a CLI debugging session can be done by using PHP command line switches or using environment variables (on the remote machine). When the SSH tunnel is up and running, we can also debug PHP CLI scripts. When a remote PHP interpreter is properly configured, it's possible to create a run/debug configuration taking advantage of the remote PHP interpreter for debugging. Debug PHP CLI scripts with remote PHP interpreters or via SSH tunnel Once we accept it, we will be able to debug using the techniques outlined in Examining a Suspended Program. When the debugger is started, PhpStorm will prompt to accept the incoming connection. Ssh -R 10137:localhost:10137 the SSH tunnel is set up, we can start debugging using zero-configuration debugging with Xdebug or Zend Debugger. Run the following command on the command line: If you are on Windows, and your operating system version doesn't have built-in SSH support, use the PuTTy SSH client instead of the command line. This can be done using the PhpStorm bookmarklets, a Browser Debugging Extension, or the techniques outlined in Debugging PHP CLI scripts with PhpStorm. In this case, we need to make the debugger connect back to the developer machine by setting xdebug.remote_host=ip_address (for Xdebug 2), xdebug.client_host=ip_address (for Xdebug 3) or making sure the debug host is the IP address of the developer machine (for Zend Debugger). When the remote server can connect to the developer machine directly (for example, with a Vagrant machine), an SSH tunnel may not be needed. The SSH tunnel is used for connecting through a firewall and establishing a secure connection between the remote server and the developer machine. The idea is to create a "virtual" TCP port on the remote server that sends its traffic to a TCP port on our own machine, tunneling traffic over SSH. What we want to do is connect to the remote machine over SSH and set up port forwarding for port 9000 (for Xdebug 2), 9003 (for Xdebug 3), or 10137 (Zend Debugger). Set up an SSH tunnel to the remote machine Before launching the script, make sure that either a breakpoint is set or the Break at first line in PHP scripts option is enabled on the Debug page of the Settings dialog Ctrl+Alt+S. This will ensure PhpStorm reacts when a debugging session is started and opens the Debug tool window automatically. In PhpStorm, enable listening to incoming debug connections by either clicking on the toolbar/the status bar or selecting Run | Start Listening for PHP Debug Connections in the main menu. Listening for incoming debugger connections When using Xdebug, make sure at least the following settings are specified: In the CLI Interpreters dialog that opens, the Configuration file read-only field shows the path to the active php.ini file. On the PHP page that opens, click next to the CLI Interpreter field. In the Settings dialog ( Ctrl+Alt+S), click PHP.
Open the active php.ini file in the editor:
Xdebug 3 phpstorm update#
To avoid this problem, you need to update the corresponding sections in the php.ini file as described in Configure Xdebug and Configure Zend Debugger. These tools cannot be used simultaneously because they block each other. PhpStorm supports debugging with two most popular tools: Xdebug and Zend Debugger. Prepare the debugging engineīefore you start debugging, make sure that you have a debugging engine installed and configured properly.
Xdebug 3 phpstorm code#
This can be useful for debugging code on a remote machine when there are firewalls in between, or a NAT router prevents direct connection, or the ISP or network infrastructure does not allow incoming TCP connections to the developer machine.
Xdebug 3 phpstorm how to#
This tutorial describes how to use an SSH tunnel to setup a secure connection between the development machine and a remote server.
0 kommentar(er)
