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

From: Date: Thu, 03 Jan 2019 08:43:04 +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-218770@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: hsiangjen at gmail dot com 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: 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. Previous Comments: ------------------------------------------------------------------------ [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? ------------------------------------------------------------------------ [2019-01-02 08:13:25] hsiangjen at gmail dot com Please download here for debug dump https://www.dropbox.com/s/1431ohhj4ikvoor/php__PID__42952__Date__01_02_2019__Time_03_58_11PM__308__Second_Chance_Exception_C000001D_CrashHangAnalysis.mht?dl=0 ------------------------------------------------------------------------ [2018-12-30 13:42:58] cmb@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. ------------------------------------------------------------------------ [2018-12-29 16:59:06] cmb@php.net Thanks for the info! ------------------------------------------------------------------------ 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 (#218770) next »