Bug #77357 [Com]: base64_encode / base64_decode doest not work on nested VM

From: Date: Thu, 03 Jan 2019 09:08:02 +0000
Subject: Bug #77357 [Com]: base64_encode / base64_decode doest not work on nested VM
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-218773@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=77357&edit=1 ID: 77357 Comment by: spam2 at rhsoft dot net Reported by: hsiangjen at gmail dot com Summary: base64_encode / base64_decode doest not work on nested VM Status: Open Type: Bug Package: *General Issues Operating System: Windows 2012R2 PHP Version: 7.3.0 Block user comment: N Private report: N New Comment: https://superuser.com/questions/453786/how-do-i-get-avx-support-in-qemu is about AVX not passed to the guest which in fact happens on your guest given "Instructions sets MMX, SSE, SSE2, SSE3, EM64T, VT-x" but in that case PHP must not use the instructions Previous Comments: ------------------------------------------------------------------------ [2019-01-03 09:01:14] hsiangjen at gmail dot com Thank you for the help. I guess since I am under KVM virtual machine enviornment. The CPU AVX instruction does not passvia to the guest level by default. I will bootup a Linux guest machine to try it also. Maybe the isseu is like this: https://superuser.com/questions/453786/how-do-i-get-avx-support-in-qemu ------------------------------------------------------------------------ [2019-01-03 08:49:36] nikic@php.net Thanks, that does look more reasonable. We're crashing inphp7ts!php_base64_encode_avx2+82 with a 0xc000001d exception, i.e. illegal instruction. Clearly we're trying to execute an AVX2 instruction on a CPU that doesn't support it. The question is why... ------------------------------------------------------------------------ [2019-01-03 08:43:04] hsiangjen at gmail dot com I chagned order version of Debug Diagonstic tool (version 1.2) Here is the dump again. https://www.dropbox.com/s/00hjbnny4hcomai/CrashHang_Report__Date_01_03_2019__Time_04_40_55PM__58.mht?dl=0 Hope this will help more. Thank you. ------------------------------------------------------------------------ [2019-01-02 09:47:26] cmb@php.net Thanks! Apparently, the actual backtrace is: php7ts!php_prefix_varname+8c82 php7ts!php_prefix_varname+88a7 php7ts!zend_ast_destroy+230 php7ts!execute_ex+5f php7ts!zend_execute+1a8 php7ts!zend_execute_scripts+b9 php7ts!php_execute_script+261 php!sapi_cli_single_write+1320 php!sapi_cli_single_write+2298 php!sapi_cli_single_write+9fa8 kernel32!BaseThreadInitThunk+22 ntdll!RtlUserThreadStart+34 The assembly instruction at php7ts!php_prefix_varname+8c82 in C:\Program Files\SaaSaMe\Transport\php_7.3\php7ts.dll from The PHP Group has caused an unknown exception (0xc000001d) ------------------------------------------------------------------------ [2019-01-02 09:45:47] nikic@php.net Stack trace says: php7ts!php_prefix_varname+8c82 php7ts!php_prefix_varname+88a7 php7ts!zend_ast_destroy+230 php7ts!execute_ex+5f php7ts!zend_execute+1a8 php7ts!zend_execute_scripts+b9 php7ts!php_execute_script+261 php!sapi_cli_single_write+1320 php!sapi_cli_single_write+2298 php!sapi_cli_single_write+9fa8 kernel32!BaseThreadInitThunk+22 ntdll!RtlUserThreadStart+34 Which doesn't look possible. Maybe the symbols weren't resolved correctly? ------------------------------------------------------------------------ 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=77357 -- Edit this bug report at https://bugs.php.net/bug.php?id=77357&edit=1

« previous php.bugs (#218773) next »