Changes

Debugging a PHP application can involve quite a bit of machinery, and effort getting that machinery setup. But it's worth it because what alternative is there? <code>echo</code>? Come on! Thanks to [http://derickrethans.nl/who.html Derick Rethans], xdebug can do a ton of cool things for you. For example, it overloads <code>[https://secure.php.net/var_dump var_dump()]</code> and gives '''you''' [http://www.xdebug.org/docs/display control over how you want deeply nested data structures to be displayed]. Once you have NetBeans and XDebug operating, you can [[CiviCRM/debugging|debug complex applications like CiviCRM]]

Here is what the wizard reported for me AFTER my recent installation of xdebug<blockquote>'''Xdebug installed:''' 2.23.3<br />'''Server API:''' Apache 2.0 Handler<br />'''Windows:''' no<br />'''Zend Server:''' no<br />'''PHP Version:''' 5.5.9-1<br />'''Zend API nr:''' 220121212<br />'''PHP API nr:''' 20121212<br />'''Debug Build:''' no<br />'''Thread Safe Build:''' no<br />'''Configuration File Path:''' /etc/php5/apache2<br />'''Configuration File:''' /etc/php5/apache2/php.ini<br />'''Extensions directory:''' /usr/lib/php5/20121212+lfs</blockquote>Caveat: the wizard can't really tell where the xdebug configuration lives (in the case of many subsidiary ini files). In Ubuntu, there might be a file in <code>/etc/php5/conf.d</code> In my case I actually did have <code>/etc/php5/conf.d/xdebug.ini</code>, but that file is superfluous because there are symbolic links for both '''apache2''' and '''cli''' that go to <code>/etc/php5/mods-available/xdebug.ini</code> (which helps PHP configuration to be the same for both runtimes.) Bottom line: run <code>locate xdebug.ini</code> to find out whether you have a duplicate/conflicting file; merge those files down to one; and make any overrides that you need from the default settings which xdebug will use if left unconfigured. Then <code>sudo service apache2 restart</code> and check the output of <code>phpinfo()</code> for correctness. The defaults are probably all good, but you may want to specify some of the following:<source lang="ini">; the old one installed by apt-get; zend_extension=/usr/lib/php5/20090626+lfs/xdebug.so; as of php 5.5 you no longer need to supply a full path to the zend_extension= token; but it doesn't hurt, and may be required if you have multiple .so files lying aroundzend_extension=/usr/lib/php5/20121212+lfs/xdebug.so ; enable debuggingxdebug.remote_enable = On; working from local machine; xdebug.remote_host = "127.0.0.1"; debugging from any machine on the local network, as well as through the routerxdebug.remote_host = "192.168.1.0/24,127.0.0.1"; set which debug client protocol we wantxdebug.remote_handler = "dbgp" ; enable anyone with access to the machine to start a debugging session; this setting also helps when you're having difficulty with the connection setup; xdebug.remote_connect_back 1 </source>

Caveat: their script Once you see xdebug in your <code>phpinfo()</code> output, you know it's enabled -- which means that you can't really tell where the already get xdebug configuration livesfunctionality out of your PHP scripts (e. g. var_dump() is overridden). But how do you get debugging working so that you can use it with your IDE? In Ubuntu, there That is a covered in the '[http://www.xdebug.org/docs/remote remote]' section of the manual. {{Highlight |text= If you want to use [https://secure.php.net/etcmanual/php5en/confopcache.d and configuration files installation.php OPcache] with Xdebug, you must load OPcache before Xdebug. In general, extensions are loaded in there add to the main order found in php.ini. So, you end up editing <code>sudo vim See https://wiki.php.net/internals/etcextensions and [https:/php5/confwiki.dphp.net/xdebug_detail/internals/extensions_lifetime.ini </code>png?id=internals%3Aextensions this graphic] for more info}}