![]() If you used the same settings that I have above, when you run PHP code, Xdebug will put the cachegrind.out files in your ‘/tmp’ directory. ![]() Doing a search in the browser window for “Xdebug” makes this easy. Check to make sure that Xdebug is running. Open MAMP’s WebStart page and navigate to PHPInfo tab. Save edited template and close edit window Now when you have errors, if they are sent to standard out, you will see something like this If you don’t want profile output and just want xdebug running then use DONT REMOVE: MAMP PRO php5.3.6.ini template compatibility version: 1 Zend_extension="/Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so" Edit the template file via File -> Edit Template -> PHP -> PHP php.iniĮdit bottom of php.ini template file so that it ends up looking like if you want profile output ![]() Here's the tutorial that helped me:Įdit php.ini template file through MAMP to enable the extension. Since release of MAMP 2.01 XDebug is already included. So I am assuming that the problem is something related to how this is set up. I notice that the port is set to 80 so wondering if that is right since the Xdebug extension is set to run over port 9000 when I click "Validate remote environment" select deployment server, then "Validate", I get: No debug extension is loaded. Only by deleting the entry that was added can I get the Incoming Connection dialogue to show up again when I refresh the page. If I then go to Settings / PHP / Servers in PhpStorm, I see that a new entry has been created: However, when I click Accept, the dialogue disappears and nothing happens. Xdebug.profiler_output_name="cachegrind.out.%p"Īfter setting a break point, turning on Xdebug chrome extension, clicking to listen to Xdebug within PhpStorm and refreshing, I get the Incoming Connection from Xdebug dialogue: I know that the Xdebug extension itself is working as the cachegrind.out.3280 files are being created on page load (with 12Mb litany of all of the scripts required and variables/values). The guides that I have used to set this up are: If PHP Tools debugging session was started before a configuration change, it is recommended to close it by exiting its systray icon or restarting Visual Studio.I have tried to set up Xdebug (2.2.3) with PhpStorm 7.0 and I cannot bring up the step-through debugging console as I have in the past. If you do not see the section above in your phpinfo output, there may be something wrong with your PHP configuration or you may need to restart your web server to let PHP update its configuration. You should see the Xdebug section in the output. Open the corresponding URL in your browser. To verify your Xdebug installation, follow these steps:Ĭreate a simple PHP file containing the following: Note that restarting nginx will not reload php.ini! You will need to restart PHP, or your server. Change Xdebug port to 9001 both in php.ini and in Visual Studio settings. Note: nginx server using FastCGI may block port 9000 by default. The default value is 9000 (For Xdebug 3 it's 9003) and it is usually enough just to leave it as it is. Xdebug.remote_port setting has to be the same as in PHP Tools options (in Visual Studio, Tools | Options | PHP Tools | Advanced).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |