Home » Configuration » Config » Bug #2951

[2004-12-12 12:53 UTC] mail at simonellistonball dot com

Description:
------------
When running PHP CLI requiring the Config.php file will
cause a segmentation fault after a long wait on Mac OS
X. This appears to be a problem with PHP itself not
properly handling the require_once command.

This can be retified by removing the unnecessary
require_once 'Config.php' line from Config/Container.php
(since config itself requires container anyway).

Reproduce code:
---------------
require 'Config.php';

[2004-12-12 14:13 UTC] bmansion at mamasam dot com

Please check that you do not have another Config.php file in your include paths that would cause the problems. I don't think your problem is related to OSX (I am on OSX myself) or PHP.

[2004-12-12 14:21 UTC] mail at simonellistonball dot com

Yes I thought that was the problem orginally too. I
checked, and there is no conflict any more :). I still
have the problem with the segfaults though. The fix of
removing the require_once Config.php in Config/
Container.php was still needed.

[2004-12-14 00:57 UTC] ryansking at mac dot com

Why not use require_once?

[2005-01-01 20:29 UTC] ryansking at mac dot com

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 PEAR.

[2005-01-30 10:50 UTC] dasher at inspiredthinking dot co dot uk

I've been noticing a weird problem that may be related.
My PHP.INI include path is: '.;d:\lib\PEAR'.
Config is at d:\lib\PEAR\Config.php and the config folder is at d:\lib\PEAR\Config;
When I try and include Config.php - sometimes the file that is included is d:\lib\PEAR\Config.php - but sometimes it is d:\lib\PEAR\PEAR\Config.php. The latter of course isn't the correct file.

[2006-12-06 01:31 UTC] aashley at php dot net

Thank you for taking the time to report a problem with PHP.
Unfortunately you are not using a current version of PHP --
the problem might already be fixed. Please download a new
PHP version from http://www.php.net/downloads.php

If you are able to reproduce the bug with one of the latest
versions of PHP, please change the PHP version on this bug report
to the version you tested and change the status back to "Open".
Again, thank you for your continued support of PEAR.

To me this looks like a bug in PHP or a misconfigured php.ini file. Please upgrade your PHP installation and try again.