Edit report at https://bugs.php.net/bug.php?id=63785&edit=1

 ID:                 63785
 User updated by:    lys0212 at qq dot com
 Reported by:        lys0212 at qq dot com
 Summary:            php-fpm segfault
 Status:             Open
 Type:               Bug
 Package:            FPM related
 Operating System:   RHEL6.3
 PHP Version:        5.3.16
 Block user comment: N
 Private report:     N

 New Comment:

(gdb) bt
#0  0x00000000007fe71a in _zend_mm_alloc_int ()
#1  0x000000000085dfaa in ZEND_ADD_ARRAY_ELEMENT_SPEC_CONST_TMP_HANDLER ()
#2  0x00007fff6629f770 in ?? ()
#3  0x0000000000000001 in ?? ()
#4  0x0000000000000003 in ?? ()
#5  0x0000000000000008 in ?? ()
#6  0x0000000000000000 in ?? ()


Previous Comments:
------------------------------------------------------------------------
[2012-12-18 02:50:53] larue...@php.net

is there any reproduce test script for this?

the bts seem randomly...

------------------------------------------------------------------------
[2012-12-17 09:39:52] lys0212 at qq dot com

When I compile PHP use parameters --enable-debug, the period of mistake won't 
appear. In return, --disable-debug this parameter compiler, it appeared again. 
This is very puzzled

------------------------------------------------------------------------
[2012-12-17 09:24:26] lys0212 at qq dot com

[New Thread 16205]
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Core was generated by `php-fpm: pool www                                        
                     '.
Program terminated with signal 11, Segmentation fault.
#0  0x000000000081ba4a in php_stat (filename=Cannot access memory at address 
0xffffffffffffed84
) at /root/php-5.3.16/ext/standard/filestat.c:861
861                             php_error_docref(NULL TSRMLS_CC, E_WARNING, 
"%sstat failed for %s", IS_LINK_OPERATION(type) ? "L" : "", filename);
Missing separate debuginfos, use: debuginfo-install 
php-cli-5.3.3-3.el6_2.8.x86_64
(gdb) bt
#0  0x000000000081ba4a in php_stat (filename=Cannot access memory at address 
0xffffffffffffed84
) at /root/php-5.3.16/ext/standard/filestat.c:861
Cannot access memory at address 0x4

------------------------------------------------------------------------
[2012-12-17 09:15:23] lys0212 at qq dot com

[root@localhost core]# gdb php -c core-php-fpm.16205
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-56.el6)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/php...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New Thread 16205]
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Core was generated by `php-fpm: pool www                                        
                     '.
Program terminated with signal 11, Segmentation fault.
#0  0x000000000081ba4a in zval_mark_grey ()
Missing separate debuginfos, use: debuginfo-install 
php-cli-5.3.3-3.el6_2.8.x86_64
(gdb) bt
#0  0x000000000081ba4a in zval_mark_grey ()
#1  0x000000000081ce07 in zend_closure_write_property ()
#2  0x0000000000000030 in ?? ()
#3  0x00000000007e060a in zend_mm_free_cache ()
#4  0x00000000007e060a in zend_mm_free_cache ()
#5  0x00007fff6c771e40 in ?? ()
#6  0x0000000000000001 in ?? ()
#7  0x7ca82b1131a2610d in ?? ()
#8  0x0000000000dba270 in ?? ()
#9  0x0000000000000000 in ?? ()
(gdb)

------------------------------------------------------------------------
[2012-12-17 06:28:38] ahar...@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.

Specifically, we're going to need a backtrace with debug information, I think.

------------------------------------------------------------------------


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=63785


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=63785&edit=1

Reply via email to