Bug #76307 [Fbk]: strftime format %Z crash php

From: Date: Tue, 08 May 2018 20:04:06 +0000
Subject: Bug #76307 [Fbk]: strftime format %Z crash php
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-215168@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=76307&edit=1 ID: 76307 Updated by: requinix@php.net Reported by: drop_box at live dot de Summary: strftime format %Z crash php Status: Feedback Type: Bug Package: Date/time related Operating System: Windows 10 1803 PHP Version: 7.2.5 Block user comment: N Private report: N New Comment: True, they won't work on Windows (should be "english_United States"), but fixing it doesn't repro for me. Today MS pushed out KB4103721 which "addresses additional issues with updated time zone information". https://support.microsoft.com/en-us/help/4103721 It brings ucrtbase.dll from version 10.0.17134.12 (at least that's what the Windows SDK has) to 10.0.17134.48. I hate to ask you to install an update as fresh as this but that changelog entry sounds suspiciously relevant. Previous Comments: ------------------------------------------------------------------------ [2018-05-08 19:15:46] cmb@php.net I'm somewhat startled regarding the setlocale() calls, since these are supposed to fail due to wrong locales, aren't they? ------------------------------------------------------------------------ [2018-05-08 18:10:48] ab@php.net That's actually same as before. The first one shows something about ext/libxml, but the second one doesn't. The common part is still in strftime, which is a function from the CRT. Unfortunately no much details, as the debug symbols are not used. You can fetch the corresponding debug symbols from https://windows.php.net/downloads/releases/ . Otherwise, i'm still scratching my head about how to reproduce it. The only laptop with this upgrade doesn't show the regression :/ Perhaps you could also check, whether you're using the latest vc15 redistributable and upgrade it if you don't? Thanks. ------------------------------------------------------------------------ [2018-05-07 13:18:06] drop_box at live dot de Now I startet directly from cli and checked all files, now looks better in my eyes: ntdll!RtlReportCriticalFailure+88 ntdll!RtlpReportHeapFailure+2f ntdll!RtlpLogHeapFailure+41 ntdll!RtlFreeHeap+48251 ucrtbase!_free_base+1b ucrtbase!__crt_unique_heap_ptr<char,__crt_internal_free_policy>::~__crt_unique_heap_ptr<char,__crt_internal_free_policy>+c ucrtbase!strftime+1a php7ts!php_strftime+1fc php7ts!zif_strftime+f php7ts!ZEND_DO_ICALL_SPEC_RETVAL_USED_HANDLER+6b php7ts!execute_ex+78 php7ts!zend_execute+152 php7ts!zend_execute_scripts+96 php7ts!php_execute_script+1f6 0x14a00000 ucrtbase!_LocaleUpdate::_LocaleUpdate+115 php7ts!php_execute_script+c1 php!do_cli+ea php!do_cli+950 0x004e0000 ------------------------------------------------------------------------ [2018-05-07 12:27:18] ab@php.net Thanks for the further info. The backtrace is mising some info due to the absence of the debug package, I guess. I can't reproduce the crash locally, however the backtrace looks familiar to that in bug #64359. It might be still the same bug in the CRT. Maybe yet some factors are relevant to reproduce the bug. Anyway, one more try could be done. I'd ask you to fetch the debug symbols and retry with the backtrace. Alternatively you could share the crash dump somewhere. Thanks. ------------------------------------------------------------------------ [2018-05-06 18:33:02] drop_box at live dot de Since i got not mutch experience in this area to do backtrace and you guide look a little bit outdated, i'm not sure if i do all right. But this looks for me as the best result: ntdll!RtlReportCriticalFailure+88 ntdll!RtlpReportHeapFailure+2f ntdll!RtlpLogHeapFailure+41 ntdll!RtlFreeHeap+48251 ucrtbase!_free_base+1b ucrtbase!__crt_unique_heap_ptr<char,__crt_internal_free_policy>::~__crt_unique_heap_ptr<char,__crt_internal_free_policy>+c ucrtbase!strftime+1a php7ts!php_strftime+1fc php7ts!xmlParserInputRead+841f php7ts!execute_internal+25 ------------------------------------------------------------------------ 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=76307 -- Edit this bug report at https://bugs.php.net/bug.php?id=76307&edit=1

« previous php.bugs (#215168) next »