Bug #71261 [Asn]: Wrong bytecode in cache of array index named 'init' containing 0 indexed subarr
| From: | jo at feuersee dot de | Date: | Sat, 02 Jan 2016 16:25:41 +0000 |
| Subject: | Bug #71261 [Asn]: Wrong bytecode in cache of array index named 'init' containing 0 indexed subarr | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-198367@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=71261&edit=1
ID: 71261
User updated by: jo at feuersee dot de
Reported by: jo at feuersee dot de
Summary: Wrong bytecode in cache of array index named 'init'
containing 0 indexed subarr
Status: Assigned
Type: Bug
Package: opcache
Operating System: Linux
PHP Version: 7.0.1
Assigned To: laruence
Block user comment: N
Private report: N
New Comment:
jo@l33t ~/tmp> valgrind php -S localhost:8080 -t
/srv/www/vhosts/www.feuersee.de/groupware/htdocs/
==20223== Memcheck, a memory error detector
==20223== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==20223== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==20223== Command: php -S localhost:8080 -t /srv/www/vhosts/www.feuersee.de/groupware/htdocs/
==20223==
PHP 7.0.1 Development Server started at Sat Jan 2 17:21:50 2016
Listening on http://localhost:8080
Document root is /srv/www/vhosts/www.feuersee.de/groupware/htdocs
Press Ctrl-C to quit.
==20223==
==20223== Process terminating with default action of signal 11 (SIGSEGV)
==20223== Bad permissions for mapped region at address 0x16951778
==20223== at 0x479C85: convert_to_boolean (in /usr/bin/php)
==20223== by 0x10BCE357: pdo_mysql_set_attribute (in /usr/lib64/php7/extensions/pdo_mysql.so)
==20223== by 0x109B43E9: pdo_dbh_attribute_set (in /usr/lib64/php7/extensions/pdo.so)
==20223== by 0x109B2656: zim_PDO_dbh_constructor (in /usr/lib64/php7/extensions/pdo.so)
==20223== by 0x51E9F1: ZEND_DO_FCALL_SPEC_HANDLER (in /usr/bin/php)
==20223== by 0x51A851: execute_ex (in /usr/bin/php)
==20223== by 0x51B1C5: zend_execute (in /usr/bin/php)
==20223== by 0x48EC4C: zend_execute_scripts (in /usr/bin/php)
==20223== by 0x3E208C: php_execute_script (in /usr/bin/php)
==20223== by 0x5FDC21: php_cli_server_dispatch_script (in /usr/bin/php)
==20223== by 0x5FEEF6: php_cli_server_dispatch (in /usr/bin/php)
==20223== by 0x5FF81A: php_cli_server_recv_event_read_request (in /usr/bin/php)
==20223== Invalid free() / delete / delete[] / realloc()
==20223== at 0x4C2A37C: free (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==20223== by 0x64AEB5B: __libc_freeres (in /lib64/libc-2.19.so)
==20223== by 0x4A2370C: _vgnU_freeres (in /usr/lib64/valgrind/vgpreload_core-amd64-linux.so)
==20223== by 0x2F: ???
==20223== by 0x10BCE357: pdo_mysql_set_attribute (in /usr/lib64/php7/extensions/pdo_mysql.so)
==20223== by 0x109B43E9: pdo_dbh_attribute_set (in /usr/lib64/php7/extensions/pdo.so)
==20223== by 0x109B2656: zim_PDO_dbh_constructor (in /usr/lib64/php7/extensions/pdo.so)
==20223== by 0x51E9F1: ZEND_DO_FCALL_SPEC_HANDLER (in /usr/bin/php)
==20223== by 0x51A851: execute_ex (in /usr/bin/php)
==20223== by 0x51B1C5: zend_execute (in /usr/bin/php)
==20223== by 0x48EC4C: zend_execute_scripts (in /usr/bin/php)
==20223== by 0x3E208C: php_execute_script (in /usr/bin/php)
==20223== Address 0x67072d0 is 0 bytes inside data symbol "noai6ai_cached"
==20223==
==20223==
==20223== HEAP SUMMARY:
==20223== in use at exit: 2,922,691 bytes in 27,842 blocks
==20223== total heap usage: 35,880 allocs, 8,039 frees, 5,101,975 bytes allocated
==20223==
==20223== LEAK SUMMARY:
==20223== definitely lost: 0 bytes in 0 blocks
==20223== indirectly lost: 0 bytes in 0 blocks
==20223== possibly lost: 2,036,653 bytes in 21,653 blocks
==20223== still reachable: 886,038 bytes in 6,189 blocks
==20223== suppressed: 0 bytes in 0 blocks
==20223== Rerun with --leak-check=full to see details of leaked memory
==20223==
==20223== For counts of detected and suppressed errors, rerun with: -v
==20223== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault
Previous Comments:
------------------------------------------------------------------------
[2016-01-02 16:17:59] jo at feuersee dot de
Would it be useful to provide a trace of PHP running with built-in webserver?
Running the script via CLI doesn't looks useful as I can't reproduce the bug there (the
opcache is invalid after execution, thus always regenerated). And Apache2 doesn't core dump at
all, can't see the problem why. This isn't my kind of cake...
------------------------------------------------------------------------
[2016-01-02 05:03:20] laruence@php.net
you can also try to make it coredump with "opcache.protect_memory=1 ", and paste the
backtrace here. thanks
------------------------------------------------------------------------
[2016-01-01 21:00:41] jo at feuersee dot de
THX. Unfortunately, the used binaries for openSUSE Leap 42.1 (from http://download.opensuse.org/repositories/devel:/languages:/php:/php7/openSUSE_Leap_42.1/)
have debug mode disabled.
I'll check over the WE wether installing PHP7 from source is less painful than changing the app
to work in CLI context.
------------------------------------------------------------------------
[2016-01-01 19:56:44] nikic@php.net
If your code is runnable using CLI, the easiest way to get a backtrace is through valgrind. Just run
valgrind php ...args...
Alternatively, using gdb run "gdb --args php ...args..." and then "r" followed
by "bt" in the gdb prompt.
If it doesn't run through cli it's probably easiest to get the backtrace from a core file,
we have some info on that here: https://bugs.php.net/bugs-generating-backtrace.php
------------------------------------------------------------------------
[2016-01-01 19:35:32] jo at feuersee dot de
Yep, it crashes with opcache.protect_memory=1 "child pid 2844 exit signal Segmentation
fault"
Unfortunately, xdebug fails to start due to API version 320151012.
Is there another convenient way to provide a backtrace?
------------------------------------------------------------------------
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=71261
--
Edit this bug report at https://bugs.php.net/bug.php?id=71261&edit=1