Bug #69199 [Fbk->NoF]: require_once doesn't require ./ files

From: Date: Sun, 20 Dec 2020 04:22:15 +0000
Subject: Bug #69199 [Fbk->NoF]: require_once doesn't require ./ files
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-231180@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=69199&edit=1

 ID:               69199
 Updated by:       php-bugs@lists.php.net
 Reported by:      pegasus at vaultwiki dot org
 Summary:          require_once doesn't require ./ files
-Status:           Feedback
+Status:           No Feedback
 Type:             Bug
 Package:          opcache
 Operating System: Centos 6 64-bit
 PHP Version:      master-Git-2015-03-07 (Git)
 Assigned To:      cmb
 Private report:   N

 New Comment:

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.


Previous Comments:
------------------------------------------------------------------------
[2020-12-07 15:57:17] cmb@php.net

Is this still an issue with any of the actively supported PHP
version[1]?  If so, do you use a thread safe (ZTS) PHP build?

[1] <https://www.php.net/supported-versions.php>

------------------------------------------------------------------------
[2015-03-27 16:06:13] pegasus at vaultwiki dot org

I also cannot reproduce this when the following ini is present:

opcache.revalidate_path=1

------------------------------------------------------------------------
[2015-03-27 15:48:43] pegasus at vaultwiki dot org

Confirmed on the latest build that this issue is only reproducible with the following ini:

opcache.use_cwd=1

The issue does not occur with:

opcache.use_cwd=0

------------------------------------------------------------------------
[2015-03-27 07:05:18] rasmus@php.net

Still unable to reproduce. I followed your steps exactly. My pass #1 and pass #3 outputs are
identical. Current PHP 7 build running php-fpm under nginx on Debian8.

------------------------------------------------------------------------
[2015-03-26 13:14:05] pegasus at vaultwiki dot org

As a follow-up, I have discovered that once this error occurs, the PHP output is used for every PHP
script in the future.

e.g. we made the error occur in main.php
But if we have another script main2.php that has completely different code and output, the previous
incorrect output of main.php is used. This explains why all the sites on my server go down together
when this error occurs on just one of them (even sites using different FPM pools).

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=69199


--
Edit this bug report at https://bugs.php.net/bug.php?id=69199&edit=1


Thread (21 messages)

« previous php.bugs (#231180) next »