Hide Forgot
abrt version: 1.1.16 architecture: x86_64 Attached file: backtrace, 32461 bytes cmdline: /usr/bin/php -d output_handler= -d open_basedir= -d safe_mode=0 -d disable_functions= -d output_buffering=Off -d error_reporting=32767 -d display_errors=1 -d display_startup_errors=1 -d log_errors=0 -d html_errors=0 -d track_errors=1 -d report_memleaks=1 -d report_zend_debug=0 -d docref_root= -d docref_ext=.html -d error_prepend_string= -d error_append_string= -d auto_prepend_file= -d auto_append_file= -d magic_quotes_runtime=0 -d ignore_repeated_errors=0 -d precision=14 -d unicode.runtime_encoding=ISO-8859-1 -d unicode.script_encoding=UTF-8 -d unicode.output_encoding=UTF-8 -d unicode.from_error_mode=U_INVALID_SUBSTITUTE -d session.auto_start=0 -d zlib.output_compression=Off -d mbstring.func_overload=0 -f /home/dkutalek/packages/php-pecl-memcache/svn/RELEASE_3_0_5/tests/044.php component: php Attached file: coredump, 5300224 bytes crash_function: _zend_mm_alloc_int executable: /usr/bin/php kernel: 2.6.32-130.el6.x86_64 package: php-cli-5.3.3-3.el6 rating: 4 reason: Process /usr/bin/php was killed by signal 11 (SIGSEGV) release: Red Hat Enterprise Linux Workstation release 6.1 Beta (Santiago) Attached file: sosreport.tar.xz, 1834208 bytes time: 1302790610 uid: 501 How to reproduce ----- 1. 2. 3.
Created attachment 492122 [details] File: backtrace
This crash is a result of running tests from php-pecl-memcache 3.0.5 sources from svn. In distribution package, these tests are not present. This test is expecting two instances of memcached running on localhost, and it is using it for php session storage. However, only one instance was running. Such situation however can occur eg. in case of network problems etc. Crash occurs also when running simply as php ./044.php - in this case it coredumps in other function, you will see.
Created attachment 492131 [details] Test which caused crash
Created attachment 492133 [details] Include for attached test
This is http://pecl.php.net/bugs/bug.php?id=13623 I have a confirmed (simple) patch. This is not a regression since 3.0.4.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0794.html