asked on

Maximum function nesting level of '100' reached, aborting!

I'm going through a Zend tutorial and when I went to my first page, I got "Fatal error: Maximum function nesting level of 100 reached."

Looking through the internet, I came across a setting that was mentioned repeatedly, that being xdebug. It was recommended that increase the xdebug.max_nesting_leve. But when I look at my ini file, this is what I see:

; XDEBUG Extension

zend_extension = "c:/wamp/bin/php/php5.5.12/zend_ext/php_xdebug-2.2.5-5.5-vc11.dll"
;
[xdebug]
xdebug.remote_enable = off
xdebug.profiler_enable = off
xdebug.profiler_enable_trigger = off
xdebug.profiler_output_name = cachegrind.out.%t.%p
xdebug.profiler_output_dir = "c:/wamp/tmp"
xdebug.show_local_vars=0

I don't have that variable. I tried to add it manually so it looked like this:

; XDEBUG Extension

zend_extension = "c:/wamp/bin/php/php5.5.12/zend_ext/php_xdebug-2.2.5-5.5-vc11.dll"
;
[xdebug]
xdebug.remote_enable = off
xdebug.profiler_enable = off
xdebug.profiler_enable_trigger = off
xdebug.profiler_output_name = cachegrind.out.%t.%p
xdebug.profiler_output_dir = "c:/wamp/tmp"
xdebug.show_local_vars=0
xdebug.max_nesting_level=250

But that didn't make any difference.

What am I missing?

Ray Paseur

There is probably a loop defining or calling functions inside of functions. You might want to turn off XDebug completely and see if the fatal error goes away. Personally I find XDebug to be a big time waster, since it can truncate important things like var_dump() output. All it really does is change the format of a few pieces of error information. A better concept to explore is phpunit, where you can get really useful information fast.

Bruce Gust

ASKER

Morning, Ray! Dang, I'm glad you're up!

Just so I do it right the first time, if my settings are as such:

zend_extension = "c:/wamp/bin/php/php5.5.12/zend_ext/php_xdebug-2.2.5-5.5-vc11.dll"
;
[xdebug]
xdebug.remote_enable = off
xdebug.profiler_enable = off
xdebug.profiler_enable_trigger = off
xdebug.profiler_output_name = cachegrind.out.%t.%p
xdebug.profiler_output_dir = "c:/wamp/tmp"
xdebug.show_local_vars=0

It looks like everything is "off," by default. How then do I turn it off?

ASKER CERTIFIED SOLUTION

Ray Paseur

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial