|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #54623 Segmentation fault after writing to first socket after closing of second socket
Submitted: 2011-04-28 16:58 UTC Modified: 2011-05-01 05:57 UTC
From: tiger dot seo at gmail dot com Assigned: cataphract (profile)
Status: Closed Package: Sockets related
PHP Version: 5.3.6 OS: Ubuntu 10.10
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: tiger dot seo at gmail dot com
New email:
PHP Version: OS:


 [2011-04-28 16:58 UTC] tiger dot seo at gmail dot com
BTW, my friend with 5.2.6 says that bug doesn`t reproduces in her, but in version 5.2.10 it does reproduced, and in version 5.3.3 also reproduced.

Backtrace from GDB:

Starting program: /usr/bin/php memcached.php
[Thread debugging using libthread_db enabled]
[New Thread 0xb7c1cb70 (LWP 11369)]
[Thread 0xb7c1cb70 (LWP 11369) exited]

Program received signal SIGSEGV, Segmentation fault.
0x080ab68a in ?? ()
(gdb) bt
#0  0x080ab68a in ?? ()
#1  0x082c9d0a in ?? ()
#2  0x0823a439 in zif_fwrite ()
#3  0x08334647 in execute_internal ()
#4  0x0092b474 in xdebug_execute_internal (current_execute_data=0x893d5bc, return_value_used=0) at /build/buildd/xdebug-2.1.0/build-php5/xdebug.c:1339
#5  0x08360310 in ?? ()
#6  0x08336fde in execute ()
#7  0x0092b123 in xdebug_execute (op_array=0x890bc14) at /build/buildd/xdebug-2.1.0/build-php5/xdebug.c:1272
#8  0x0830cf06 in zend_execute_scripts ()
#9  0x082b1654 in php_execute_script ()
#10 0x083a41bb in ?? ()
#11 0x00646ce7 in __libc_start_main () from /lib/
#12 0x08066ca1 in _start ()

Test script:

$sock = pfsockopen('', '11211');
$data = "add 1_".md5(time())." 0 10 10\r\n".time()."\r\n";
fwrite($sock, $data);
$sock2 = pfsockopen('', '11211');
$data2 = "add 2_".md5(time())." 0 10 10\r\n".time()."\r\n";
fwrite($sock2, $data2);
$data = "add 3_".md5(time())." 0 10 10\r\n".time()."\r\n";
fwrite($sock, $data);

Expected result:
Data normally writed to first socket

Actual result:
Program received signal SIGSEGV, Segmentation fault.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2011-04-28 17:08 UTC] tiger dot seo at gmail dot com
Port can be any other, for example with 80 port bug is reproduced
 [2011-04-30 18:49 UTC]
-Assigned To: +Assigned To: cataphract
 [2011-04-30 22:00 UTC]
Looks like a persistent version of bug #24557 (see r136199 and r136088).
 [2011-05-01 05:57 UTC]
Automatic comment from SVN on behalf of cataphract
Log: - Fixed bug #54623 (Segfault when when writing to a persistent socket after
  closing a copy of the socket).
 [2011-05-01 05:57 UTC]
-Status: Assigned +Status: Closed
 [2011-05-01 05:57 UTC]
Fixed in SVN. Thanks for the report.
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Sun Jun 04 05:03:39 2023 UTC