Bug #52752 [Com]: Crash when lexing

Edit report at https://bugs.php.net/bug.php?id=52752&edit=1 ID: 52752 Comment by: fbastani at perennate dot com Reported by: paulgao at yeah dot net Summary: Crash when lexing Status: Duplicate Type: Bug Package: Scripting Engine problem Operating System: Centos 5 32bit PHP Version: 5.3SVN-2010-08-31 (SVN) Block user comment: N Private report: N New Comment: I am still encountering this bug with PHP 5.5.9, using php5-fpm without opcache/APC. Backtrace: #0 lex_scan (zendlval=zendlval@entry=0x7fffefa33e58) at Zend/zend_language_scanner.c:2271 #1 0x00000000006d7772 in zendlex (zendlval=zendlval@entry=0x7fffefa33e50) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_compile.c:6749 #2 0x00000000006b2766 in zendparse () at /build/buildd/php5-5.5.9+dfsg/Zend/zend_language_parser.c:3438 #3 0x00000000006b7d18 in compile_file (file_handle=file_handle@entry=0x7fffefa36330, type=8) at Zend/zend_language_scanner.l:588 #4 0x00000000006dd4ea in dtrace_compile_file (file_handle=0x7fffefa36330, type=<optimized out>) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_dtrace.c:40 #5 0x0000000000566674 in phar_compile_file (file_handle=<optimized out>, type=<optimized out>) at /build/buildd/php5-5.5.9+dfsg/ext/phar/phar.c:3379 #6 0x000000000079cb9d in ZEND_INCLUDE_OR_EVAL_SPEC_TMP_HANDLER (execute_data=0x7fc1d68e6688) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_vm_execute.h:7994 #7 0x00000000007173e8 in execute_ex (execute_data=0x7fc1d68e6688) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_vm_execute.h:363 #8 0x00000000006dd559 in dtrace_execute_ex (execute_data=<optimized out>) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_dtrace.c:73 #9 0x000000000079d1bf in ZEND_INCLUDE_OR_EVAL_SPEC_CONST_HANDLER (execute_data=0x7fc1d68e60f8) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_vm_execute.h:2748 #10 0x00000000007173e8 in execute_ex (execute_data=0x7fc1d68e60f8) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_vm_execute.h:363 #11 0x00000000006dd559 in dtrace_execute_ex (execute_data=<optimized out>) at /build/buildd/php5-5.5.9+dfsg/Zend/zend_dtrace.c:73 #12 0x00000000006eefe0 in zend_execute_scripts (type=type@entry=8, retval=retval@entry=0x0, file_count=file_count@entry=3) at /build/buildd/php5-5.5.9+dfsg/Zend/zend.c:1316 #13 0x000000000068eec5 in php_execute_script (primary_file=primary_file@entry=0x7fffefa38ad0) at /build/buildd/php5-5.5.9+dfsg/main/main.c:2506 #14 0x0000000000463b00 in main (argc=<optimized out>, argv=<optimized out>) at /build/buildd/php5-5.5.9+dfsg/sapi/fpm/fpm/fpm_main.c:1933 Line 2271 is this switch statement: YYDEBUG(121, *YYCURSOR); YYFILL(16); yych = *YYCURSOR; YYDEBUG(-1, yych); 2271 switch (yych) { case 0x00: case 0x01: case 0x02: case 0x03: This bug is marked duplicate, but all of the references bugs also appear to be marked duplicate. The error does not happen on every request, but occurs several ten or so times a day on our webserver. The file being compiled is "/var/www/include/include.php", which is included on every request, so there does not appear to be anything special about the requests that are failing (usually it is just a GET request for a static page that's parsed through PHP). Previous Comments: ------------------------------------------------------------------------ [2014-12-04 12:05:38] kostik dot lv at gmail dot com It's marked as a duplicate to itself: [2013-07-24 10:12 UTC] ab@php.net -Status: Open +Status: Duplicate [2013-07-24 10:12 UTC] ab@php.net see bug #52752 ------------------------------------------------------------------------ [2014-12-04 12:05:38] kostik dot lv at gmail dot com Related To: Bug #52752 ------------------------------------------------------------------------ [2014-11-19 15:00:13] igor at wiedler dot ch Which bug is this a duplicate of? From what I can tell, all related bugs have been closed. Was this one closed by accident? ------------------------------------------------------------------------ [2013-07-24 10:19:36] ab@php.net Related To: Bug #64883 ------------------------------------------------------------------------ [2013-07-24 10:16:12] ab@php.net Related To: Bug #64996 ------------------------------------------------------------------------ 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=52752 -- Edit this bug report at https://bugs.php.net/bug.php?id=52752&edit=1