I’ve found a more modern and easier solution partially based on CrasyCoder’s post. The steps you need to do are the following: If your brand new php installation doesn’t contain php.ini, rename the php.ini-development to php.ini Install xdebug with help of the wizard: http://xdebug.org/wizard.php Follow its recommendations literally. Put in your php.ini the string: xdebug.remote_enable=1 … Read more
I found the problem was Xdebug in xampp\php\php.ini. Here’re the results of trying many solutions found around the web: Run XAMPP as adminisrator and restart server: 3617 ms In xampp/apache/conf/httpd.conf, replace localhost with 127.0.0.1 and restart server: 3639 ms In Windows/System32/drivers/etc/hosts, add “127.0.0.1 127.0.0.1” & “127.0.0.1 localhost” and restart Windows: 3960 ms In Windows/System32/drivers/etc/hosts, un-comment … Read more
You are using Xdebug v3 but keep using Xdebug v2 config parameters. You need to go through Upgrading from Xdebug 2 to 3 Guide and adjust your settings. Xdebug v3 uses different config params than Xdebug v2 (your phpinfo() output tells you exactly that on your screenshot). 5 out of 6 “xdebug.” params from your … Read more
Besides the obvious fact that debug messages cannot be displayed in a application that is already in production, and also the fact that I don’t know why would you like that, there a couple of things really bad about it. The first one is that when you add debugging behavior to your server, the debug … Read more
Have you rectified the issue ? If not then please try this. 1.) php.ini file content [xDebug] zend_extension = “c:\xampp\php\ext\php_xdebug-2.2.3-5.4-vc9.dll” xdebug.remote_autostart=on xdebug.remote_enable=on xdebug.remote_enable=1 xdebug.remote_handler=”dbgp” ;xdebug.remote_host=”localhost:81″ xdebug.remote_host=192.168.1.5 ;xdebug.remote_connect_back=1 xdebug.remote_port=9000 xdebug.remote_mode=req xdebug.idekey=”netbeans-xdebug” xdebug.remote_host=192.168.1.5 – This is the IPv4 address of my system, I changed to this because I couldn’t debug with localhost and 127.0.0.1. in NetBeans IDE, … Read more
You can use one of these approaches: Configure your Xdebug (by editing php.ini) to attempt to debug every PHP script. The key option: Xdebug v2: xdebug.remote_autostart = 1 Xdebug v3: xdebug.start_with_request = yes Add Xdebug session start parameter to the actual URL (XDEBUG_SESSION_START={{KEY}} — https://xdebug.org/docs/step_debug#manual-init), for example: ?XDEBUG_SESSION_START=PHPSTORM Pass Xdebug cookie as part of the … Read more
These are configurable variables in php.ini: ; with sane limits xdebug.var_display_max_depth = 10 xdebug.var_display_max_children = 256 xdebug.var_display_max_data = 1024 ; with no limits ; (maximum nesting is 1023) xdebug.var_display_max_depth = -1 xdebug.var_display_max_children = -1 xdebug.var_display_max_data = -1 Of course, these may also be set at runtime via ini_set(), useful if you don’t want to modify … Read more
Find your php.ini and look for XDebug. Set xdebug autostart to false xdebug.remote_autostart=0 xdebug.remote_enable=0 Disable your profiler xdebug.profiler_enable=0 Note that there can be a performance loss even with xdebug disabled but loaded. To disable loading of the extension itself, you need to comment it in your php.ini. Find an entry looking like this: zend_extension = … Read more
This error message comes specifically from the XDebug extension. PHP itself does not have a function nesting limit. Change the setting in your php.ini: xdebug.max_nesting_level = 200 or in your PHP code: ini_set(‘xdebug.max_nesting_level’, 200); As for if you really need to change it (i.e.: if there’s a alternative solution to a recursive function), I can’t … Read more
Increase the value of xdebug.max_nesting_level in your php.ini