Step into code located inside phar-files (eg. So, with 9 extra characters to type I now have an easy way to enable the debugger for just one execution. The sub-shell demarcated by the parentheses will keep the environment-variable from “escaping” to its parent shell. If I want to enable/disable debugging for the remained of the shells lifetime I can use the aliases by themselves, but what I’ve actually ended up doing is running the alias in a sub-shell together with the command I want to debug like this: $ (xdb & drush some-command) I have ended up using a simple shell-alias:Īlias xdb='export XDEBUG_CONFIG='profiler_enable=1'' alias xdb_off='export XDEBUG_CONFIG='profiler_enable=0'' The main disadvantage here is that you have to remember the exact syntax. $ XDEBUG_CONFIG='profiler_enable=1' drush status simultaneous debugging sessions.Īnother approach is to set the environment for just one PHP-execution, eg. The problem here is if you forget that you have enabled debugging, you might then later on run into the issue with eg. So if you do this: $ export XDEBUG_CONFIG='profiler_enable=1'Īll PHP-processes executed from the shell will have debugging enabled. When starting up xdebug will examine the “XDEBUG_CONFIG” environment-variable for configuration-settings that should override configurations set via php.ini. On the commandline the easiest way to control whether XDebug is enabled is via environment variables. On the web-side we have browser-plugins to help controlling when debugging should be enabled. default as it will slow down PHP-execution. You usually don’t want debugging to be enabled pr. Last but not least, if you are not using Xdebug for your PHP-development, read this.Īnd now, without any further ado, on to the tricks: Switching xdebug on and off on the commandline Head over to XDEBUG Y U NO WORK - you might be in luck and this is what you’ve been looking for. If you’ve had problems getting Xdebug up and running I have some general links and two specific troubleshooting tips for you. If you need a brushup on how Xdebug and the IDE interacts take a look at “ How Xdebug communicates with the IDE” - You might need it for the last tip. I’ll get to the tips in just a moment, but first a couple of extra tidbits I ended up writing while describing the tips, that you might find useful. Just ignore any mentions of 'drush' and 'Drupal' and you will be fine :) While I worked out the most of these tricks while doing Drupal-development with Phpstorm - the majority should be applicable for debugging most PHP-applications. This blogpost offers tips and tricks for debugging PHP applications.

Phpstorm show line numbers