Bug #71910 [Fbk->Opn]: Too many concatinations in a single statement crashes Apache
| From: | ksours at internebrands dot com | Date: | Mon, 04 Apr 2016 22:42:52 +0000 |
| Subject: | Bug #71910 [Fbk->Opn]: Too many concatinations in a single statement crashes Apache | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-200361@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=71910&edit=1
ID: 71910
User updated by: ksours at internebrands dot com
Reported by: ksours at internebrands dot com
Summary: Too many concatinations in a single statement
crashes Apache
-Status: Feedback
+Status: Open
Type: Bug
Package: Apache2 related
Operating System: Windows7 64bit
PHP Version: 7.0.4
Block user comment: N
Private report: N
New Comment:
Also note that the screen shots in your debug doc are out of date. The new tool has a separate
analysis app (and you need to set the debug symbols in both)
Previous Comments:
------------------------------------------------------------------------
[2016-04-04 22:41:16] ksours at internetbrands dot com
Note that I've removed a large number of repeated lines because its quite long and I think you
get the message. Total line count of the traces is 2508.
Entry point libhttpd!ap_run_generate_log_id+3db0
Create time 4/4/2016 6:15:01 PM
Time spent in user mode 0 Days 00:00:00.000
Time spent in kernel mode 0 Days 00:00:00.031
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads
may be required.
php7ts!zend_compile_binary_op+10
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
...
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_binary_op+33
php7ts!zend_compile_expr+155
php7ts!zend_compile_assign+a5
php7ts!zend_compile_expr+125
php7ts!zend_compile_stmt+162
php7ts!zend_compile_top_stmt+23
php7ts!zend_compile_top_stmt+9c
php7ts!compile_file+17e
php7ts!phar_compile_file+30c
php7ts!zend_execute_scripts+86
php7ts!php_execute_script+4c6
php7apache2_4!php_handler+579
libhttpd!ap_run_handler+35
libhttpd!ap_invoke_handler+110
libhttpd!ap_internal_redirect_handler+29a
libhttpd!ap_process_request+17
libhttpd!ap_byterange_filter+152f
libhttpd!ap_run_process_connection+35
libhttpd!ap_run_generate_log_id+3f24
kernel32!BaseThreadInitThunk+d
ntdll!RtlUserThreadStart+1d
Exception Information
PHP7TS!ZEND_COMPILE_BINARY_OP+10In
httpd__PID__11296__Date__04_04_2016__Time_06_16_39PM__900__Second_Chance_Exception_C00000FD.dmp the
assembly instruction at php7ts!zend_compile_binary_op+10 in
C:\programming\applications\php704_64\php7ts.dll from The PHP Group has caused a stack overflow
exception (0xC00000FD) when trying to write to memory location 0x02643ff8 on thread 3
------------------------------------------------------------------------
[2016-03-29 16:33:08] ksours at internetbrands dot com
It doesn't seem to matter if its there or not. I left it in because it's weirder that
way. I will attempt to download the tool and get the stacktrace.
------------------------------------------------------------------------
[2016-03-29 16:28:49] ab@php.net
Yeah, it was linking to an older tool version. I've just updated it, it should be https://www.microsoft.com/en-us/download/details.aspx?id=49924
.
Ok, so you mean the presence of exit; is explicitly required to reproduce the crash. I reproduced no
issue neither with nor without it, that's why i mentioned it. So it'd be better to see the
backtrace it shows for you.
Thanks.
------------------------------------------------------------------------
[2016-03-29 15:04:46] ksours at internebrands dot com
Attempted to download the diagnostic tool from the link your provided. Got directed here.
https://www.microsoft.com/library/errorpages/smarterror.aspx
------------------------------------------------------------------------
[2016-03-29 14:40:48] ksours at internetbrands dot com
The exit is intentional, as I noted in my initial report. The script, as generated, will crash
Apache. It also doesn't matter if there are parse errors or non existent functions -- at least
in certain places -- within the script. I didn't spend a lot of time investigating that, it
was just something I noticed while simplifying the script.
------------------------------------------------------------------------
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=71910
--
Edit this bug report at https://bugs.php.net/bug.php?id=71910&edit=1