Bug #70435 [Fbk]: Wrong return type when opcache is enabled

Edit report at https://bugs.php.net/bug.php?id=70435&edit=1 ID: 70435 Updated by: peehaa@php.net Reported by: peehaa@php.net Summary: Wrong return type when opcache is enabled Status: Feedback Type: Bug Package: opcache Operating System: Windows 7 PHP Version: 7.0.0RC2 Block user comment: N Private report: N New Comment: I forgot to ask you Anatol. What environment did you test it on? Previous Comments: ------------------------------------------------------------------------ [2015-09-25 15:32:42] peehaa@php.net I tried with RC3 as well, same problem. I will try to set up some debugging tools on my machine this weekend and find out whether I can provide more info. Will let you know and thanks for looking into it so far. ------------------------------------------------------------------------ [2015-09-25 10:48:38] ab@php.net @peehaa I've just pulled your reproduce repo, testing with the todays PHP-7.0, but cannot reproduce it. Either it has been fixed inbetween by something else, or i'm doing something wrong. Please check again with some recent snapshots (or ping if you need me to provide one). Thanks. ------------------------------------------------------------------------ [2015-09-06 16:28:25] peehaa@php.net I realized the repro code is larger than optimal laurence. As stated in my OP I have tried to isolate and minimize the problem code as far as I could. The fact that it is about opcache heisenbugs also doesn't really help. I tried to make it as easy and convenient as possible by creating a repo for it which can just be run on a webserver without much hassle. If you have any idea how I could submit a couple of lines with the problem code which starts with <?php and ends with ?> I am more than happy to provide it, but as of now I have no idea how I could possibly fulfill your request. ------------------------------------------------------------------------ [2015-09-06 16:18:15] danack@php.net Laruence, the bug appears to only happen when there are multiple scripts involved. It does not happen inside a single script. Can you give some more usable advice on how to proceed, rather than insisting on it being demonstrated in a single script? The reporter is known to be reasonably competent, they'll be able to follow your instructions...but they aren't able to reproduce a bug under conditions where it is known not to occur. ------------------------------------------------------------------------ [2015-09-06 15:47:00] laruence@php.net Thank you for this bug report. To properly diagnose the problem, we need a short but complete example script to be able to reproduce this bug ourselves. A proper reproducing script starts with <?php and ends with ?>, is max. 10-20 lines long and does not require any external resources such as databases, etc. If the script requires a database to demonstrate the issue, please make sure it creates all necessary tables, stored procedures etc. Please avoid embedding huge scripts into the report. ------------------------------------------------------------------------ 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=70435 -- Edit this bug report at https://bugs.php.net/bug.php?id=70435&edit=1