Refer to the Xdebug documentation for details. In the Xdebug configuration, make sure xdebug.remote_host and xdebug.remote_port ( xdebug.client_host and xdebug.client_port for Xdebug 3) are correct. Make sure Xdebug or Zend Debugger are configured to connect to the host and port PhpStorm is running on. When the debugger cannot connect or refuses the connection, check the following: If any errors or warnings are present on the first lines, it's recommended to fix them before continuing. The PHP Group Zend Engine v3.1.0, Copyright (c) 1998-2018 Zend Technologies with Zend OPcache v7.1.20,Ĭopyright (c) 1999-2018, by Zend Technologies with Xdebug v2.6.0, Copyright (c) 2002-2018, by Derick Rethans To verify that no startup warnings or errors are displayed, run the following command: PhpStorm will also not be able to recognize the debugger being used. When this is the case, the debugger may fail to work. When running PHP, it can happen that a startup warning or error is displayed.
To validate the debugging engine configuration, perform the steps described in Validate the Configuration of a Debugging Engine Startup warnings and errors preventing the debugger from working
#Close window code for html executable 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.
To debug PHP code with PhpStorm, make sure that you have a debugging engine, either Xdebug or Zend Debugger, installed and configured properly. Making sure Xdebug or Zend Debugger are installed and configured When logging is no longer needed, it is recommended to disable it. The log file will not automatically roll-over or be truncated and may grow to a vast file size.
0 kommentar(er)
