Re: PHP-FPM: SIGSEGV during Exception generation

On 31-3-2015 15:38, B. R. wrote:

Hello, We are experiencing SIGSEGV with PHP-FPM (v5.4 from Red Hat Software Collections). Here are the details: $ cat /etc/centos-release CentOS release 6.6 (Final) $ php-fpm -v PHP 5.4.16 (fpm-fcgi) (built: Nov 19 2014 10:23:12) Copyright (c) 1997-2013 The PHP Group Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies $ gdb coredump [...] Program terminated with signal 11, Segmentation fault. #0 0x00000000006523d1 in ZEND_INIT_STATIC_METHOD_CALL_SPEC_CONST_CONST_HANDLER

     (execute_data=0x7f28c58e8c50)
     at /usr/src/debug/php-5.4.16/Zend/zend_vm_execute.h:3510
3510                                    zend_error_noreturn(E_ERROR,

"Non-static method %s::%s() cannot be called statically, assuming $this from incompatible context", EX(fbc)->common.scope->name, EX(fbc)->common.function_name); Missing separate debuginfos, use: debuginfo-install libidn-1.18-2.el6.x86_64 libmcrypt-2.5.8-9.el6.x86_64 bt full is of no use for use. Do you wish to have it? Using .gdbinit for v5.4.16 from php-src GitHub repository, I found where the error is generated, and it is indeed a static call to a method (which might not be statically defined). No information there: code error, that is right, but no reason for any segmentation fault to occur. ​I know v5.4.16​ is far from being the latest version of the branch, however, it is being used as shipped by a stable distro, thus believed to be... stable. ​ Any idea how to solve the problem?​ Thanks, --- *B. R.*

Well, simply put... 5.4 is NOT a stable branch; it's an old-stable and currently in security-releases-only-mode until September 14th when it will reach its end-of-life. Secondly, 5.4.16 is an OLD version. The most up-to-date version of 5.4 would be 5.4.39. The fact that RedHat ships it as stable does not mean it IS the latest stable release. What I would suggest is testing this again, with the latest versions (5.4.39 and 5.6.7), to see if the problem is still there. If so > post a bug report at http://bugs.php.net/, if it's gone: well, you know what to do then :) (upgrade to the latest PHP version...). - Tul --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com