php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #22482 Fatal error: Nesting level too deep - recursive dependency? in Unknown on line
Submitted: 2003-02-28 18:15 UTC Modified: 2003-03-04 19:38 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:0 (0.0%)
From: submissions at spherious dot com Assigned:
Status: Not a bug Package: *General Issues
PHP Version: 4.3.1 OS: Linux 7.2, Zend 2.1
Private report: No CVE-ID: None
 [2003-02-28 18:15 UTC] submissions at spherious dot com
Even just a simple phpinfo

<?
phpinfo();
?>

Leaves this error on the bottom of the page:

Fatal error: Nesting level too deep - recursive dependency? in Unknown on line 0

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-02-28 18:43 UTC] magnus@php.net
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.


And what is that Zend 2.1 ?
 [2003-02-28 19:33 UTC] submissions at spherious dot com
I've upgraded to PHP 4.3.1 (from 4.2.2). The install went without a hitch.

Now, any php file at all leaves the error i mentioned on the bottom of the page, rendering PHP unusable. 

By Zend I mean Zend Optimizer v2.1.0. I don't think it is related to the problem.
 [2003-02-28 19:56 UTC] magnus@php.net
Try without Zend Optimizer.
 [2003-02-28 20:06 UTC] submissions at spherious dot com
Unfortunately, I cant to that. I've had to revert back to 4.2.2 for the time being (until this can be sorted out). The machine hosts over 100 web sites, so I can't take the time to re-try this and risk my customers sites not working.

Also, I have some customers that require Zend optimizer.
 [2003-02-28 20:34 UTC] nospam_webmaster at greenliquid dot com
I have this same problem running under RedHat 8.0 with Apache 2.0.40 and PHP 4.3.1 (which it was just updated to today from 4.3.0Dev)

I renamed a simple html file as a php file and it generated the error. Even with no php code in the file.

You can see it at:
http://www (dot) clearliquid (dot) com/phpinfo.php
Scroll to the very bottom.

I hope this helps.
 [2003-02-28 20:54 UTC] magnus@php.net
Take a look at bug 21333 and 21825.
Does this solve it ?
 [2003-02-28 21:04 UTC] submissions at spherious dot com
Those bugs mention that it is linking to the old modules, which may well be the problem.

However, there are no .so files in /usr/lib/php. Just a directory called build which does not appear to contain .so files either. If the correct ones are not in /usr/lib/php4, then how can I find out where the correct ones are?
 [2003-02-28 21:37 UTC] magnus@php.net
You can find out that from the configuration line used.
The change your extension_dir configuration option to point to that directory. 
 [2003-03-02 09:46 UTC] submissions at spherious dot com
Ok, I think the error is extension related, but I don't know in what way.

I deleted all in /usr/lib/php4 then recompiled php4.3.1, but the error still occurs, so it is not linking to old files.

If I link it to something else, the error does not occur, but of course this would mean the extensions aren't loaded.
 [2003-03-02 19:29 UTC] magnus@php.net
Do you have redhat's RPMs installed ?

If you install it with just a --prefix=/usr/local/php, does
it still print out the error?
 [2003-03-03 19:57 UTC] sniper@php.net
Check what php.ini is loaded and what extensions are loaded by it..this is not really bug but just install/configure error.

 [2003-03-03 20:27 UTC] submissions at spherious dot com
I think it is a bug, because as far as I can see, there is no configure error. The php.ini references the direcotry containing the new ext files that are created when php is compiled, make and make intalled, so there is no error in configuration. I have also tried deleting everything in /usr/lib/php4 and then recompiling. It creates the new files there as it should, but still does not solve the problem.

I will try installing with just --prefix=/usr/local/php tonight. I expect that will not cause an error, as no extensions will be used. If that is the case, unfortunately, that still won't solve the problem.
 [2003-03-03 20:51 UTC] sniper@php.net
Loading old modules with new PHP versions is not bug
but configuration error by you. Please check WHAT php.ini file is actually used and what in THAT file is said for being the extension path and what extensions are loaded.

And it doesn't work vice-versa either, (loading new modules with old PHP versions) so check that you're really loading the new PHP version.


 [2003-03-04 08:25 UTC] submissions at spherious dot com
Ok, i'm not sure on what you are basing your assumption that i am not configuring it correctly. I think this is a bug, with the install script.

I've done further testing and found that the error was only present when pgsql.so was loaded. The other modules did not cause the error. Therefore, it first appeared to be a bug in either the way php linked to this file, or the way it created it.

Just for interests sake, I did an ls -l on the files that had been created in /usr/lib/php4 and compared to those in (install dir)/php-4.3.1/modules/. I found that, to my surprise, the files were different sizes. I checked the file sizes for the previous installation (php-4.2.2) and they were different again (so it wasn't the old files). 

Somehow, the php-4.3.1 configure, make, make install, was copying files to the /usr/lib/php4 directory that were different than those located in (install dir)/php-4.3.1/modules/. Correct me if i'm wrong, but that sounds like a bug to me. I did a manual copy of the files from (install dir)/php-4.3.1/modules/ to /usr/lib/php4, and the problems are gone.
 [2003-03-04 19:38 UTC] sniper@php.net
The modules are not installed in such directories.
Per default they go in pretty cryptic place, thus you're
just looking in the wrong place.

 [2003-03-11 08:21 UTC] stevester at freeuk dot com
I had this exact error message when I upgraded PHP to 4.3.0 on Mandrake 9.0. I had pgsql as a loadable module in my php.ini file, HOWEVER, I do not have pgsql support enabled on my php build. Comment out the extension = pgsql.so line and the problem was fixed. I don't know if it's just pgsql, or any extension you attempt to load when it's not built in.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved.
Last updated: Wed Aug 06 09:00:02 2025 UTC