Bug #74369 [Fbk->Csd]: Random segmentation fault (core dumped)

Edit report at https://bugs.php.net/bug.php?id=74369&edit=1 ID: 74369 User updated by: sexecut at gmail dot com Reported by: sexecut at gmail dot com Summary: Random segmentation fault (core dumped) -Status: Feedback +Status: Closed Type: Bug Package: Reproducible crash Operating System: Ubuntu 16.04.1 LTS PHP Version: 7.1.3 Block user comment: N Private report: N New Comment: Close Previous Comments: ------------------------------------------------------------------------ [2017-04-04 12:39:33] sexecut at gmail dot com The problem was solved by accident. After installing valgrind apt-get deleted the library, the result was an error: > Php: error while loading shared libraries: libc-client.so.2007e: can not open shared object > file: No such file or directory I returned back this library and at the same time updated all the packages of the system and php started working fine! Next time I will update the system packages before updating the version of php. Sorry for the lost time ------------------------------------------------------------------------ [2017-04-04 12:17:40] sexecut at gmail dot com > php: error while loading shared libraries: libc-client.so.2007e: cannot open shared object > file: No such file or directory Oops, php build is broken now I try reinstall it ------------------------------------------------------------------------ [2017-04-04 11:14:32] sexecut at gmail dot com Thanks for reply. I completely forgot. On version 7.1.0 everything all was fine > Can you provide the result of running the code under "USE_ZEND_ALLOC=0 valgrind php"? $ USE_ZEND_ALLOC=0 valgrind php ==64544== Memcheck, a memory error detector ==64544== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==64544== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==64544== Command: php ==64544== php: error while loading shared libraries: libc-client.so.2007e: cannot open shared object file: No such file or directory ==64544== Jump to the invalid address stated on the next line ==64544== at 0x566: ??? ==64544== by 0x401026C: _dl_signal_error (dl-error.c:125) ==64544== by 0x400EE89: _dl_map_object_deps (dl-deps.c:686) ==64544== by 0x40034F9: dl_main (rtld.c:1610) ==64544== by 0x4019461: _dl_sysdep_start (dl-sysdep.c:249) ==64544== by 0x4004E79: _dl_start_final (rtld.c:307) ==64544== by 0x4004E79: _dl_start (rtld.c:413) ==64544== by 0x4000CC7: ??? (in /lib/x86_64-linux-gnu/ld-2.23.so) ==64544== Address 0x566 is not stack'd, malloc'd or (recently) free'd ==64544== ==64544== ==64544== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==64544== Bad permissions for mapped region at address 0x566 ==64544== at 0x566: ??? ==64544== by 0x401026C: _dl_signal_error (dl-error.c:125) ==64544== by 0x400EE89: _dl_map_object_deps (dl-deps.c:686) ==64544== by 0x40034F9: dl_main (rtld.c:1610) ==64544== by 0x4019461: _dl_sysdep_start (dl-sysdep.c:249) ==64544== by 0x4004E79: _dl_start_final (rtld.c:307) ==64544== by 0x4004E79: _dl_start (rtld.c:413) ==64544== by 0x4000CC7: ??? (in /lib/x86_64-linux-gnu/ld-2.23.so) ==64544== ==64544== HEAP SUMMARY: ==64544== in use at exit: 0 bytes in 0 blocks ==64544== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==64544== ==64544== All heap blocks were freed -- no leaks are possible ==64544== ==64544== For counts of detected and suppressed errors, rerun with: -v ==64544== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ------------------------------------------------------------------------ [2017-04-04 11:04:14] spam2 at rhsoft dot net > A proper reproducing script starts with <?php > and ends with ?>,is max. 10-20 lines long well, but when it happens only with a large script that's just impossible and that standard paragrpah not very helpful ------------------------------------------------------------------------ [2017-04-04 11:01:23] nikic@php.net Can you provide the result of running the code under "USE_ZEND_ALLOC=0 valgrind php"? ------------------------------------------------------------------------ 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=74369 -- Edit this bug report at https://bugs.php.net/bug.php?id=74369&edit=1