发表新帖

A bug occurred in Swoole-v4.5.6

### 问题描述
在BurpSuite的攻击测试中，worker线程经常的崩溃，直到core文件撑爆硬盘

### Swoole版本，PHP版本，以及操作系统版本信息
docker alpine:3.11
/ # uname -a
Linux 242eb7add278 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017 x86_64 Linux
/ # php -v
PHP 7.4.9 (cli) (built: Aug 31 2020 18:06:19) ( NTS )

### 相关代码

### 你期待的结果是什么？实际看到的错误信息又是什么？

典型的core有两类，我直接贴出来了
#####CoreDump 1

/ # gdb php core.119
...
Reading symbols from php...
(No debugging symbols found in php)

warning: core file may not match specified executable file.
[New LWP 119]
[New LWP 120]
[New LWP 122]
[New LWP 123]
[New LWP 121]

warning: Can't read pathname for load map: No error information.
Core was generated by `Worker.1 '.
Program terminated with signal SIGSEGV, Segmentation fault.
/#0 0x00007f2e7c40ac0b in ?? () from /lib/ld-musl-x86_64.so.1
[Current thread is 1 (LWP 119)]
(gdb) bt
/#0 0x00007f2e7c40ac0b in ?? () from /lib/ld-musl-x86_64.so.1
/#1 0x00007f2e6eea04e8 in ?? ()
/#2 0x00007f2e6f40c0d8 in ?? ()
/#3 0x00007f2e6eea1ca0 in ?? ()
/#4 0x00007f2e7c410f50 in write () from /lib/ld-musl-x86_64.so.1
/#5 0x0000000000000000 in ?? ()
(gdb) f 1
/#1 0x00007f2e6eea04e8 in ?? ()
(gdb) f 0
/#0 0x00007f2e7c40ac0b in ?? () from /lib/ld-musl-x86_64.so.1

#####CoreDump 2
/ # gdb php core.78
Reading symbols from php...
(No debugging symbols found in php)

warning: core file may not match specified executable file.
[New LWP 78]
[New LWP 95]
[New LWP 96]
[New LWP 94]
[New LWP 97]

warning: Can't read pathname for load map: No error information.
Core was generated by `Worker.3 '.
Program terminated with signal SIGSEGV, Segmentation fault.
/#0 0x0000564c566ea0ae in sapi_cli_single_write ()
[Current thread is 1 (LWP 78)]

(gdb) bt

/#0 0x0000564c566ea0ae in sapi_cli_single_write ()
/#1 0x0000564c566ea17d in ?? ()
/#2 0x0000564c56638f69 in ?? ()
/#3 0x0000564c56638fc2 in php_output_write ()
/#4 0x0000564c566b0dc2 in ?? ()
/#5 0x0000564c566e3a7a in execute_ex ()
/#6 0x0000564c5666e36c in zend_call_function ()
/#7 0x0000564c565ce959 in ?? ()
/#8 0x0000564c566dfe1b in execute_ex ()
/#9 0x0000564c5666e36c in zend_call_function ()
/#10 0x0000564c565ce959 in ?? ()
/#11 0x0000564c566dfe1b in execute_ex ()
/#12 0x0000564c5666e36c in zend_call_function ()
/#13 0x0000564c565ce959 in ?? ()
/#14 0x0000564c566dfe1b in execute_ex ()
/#15 0x0000564c5666e36c in zend_call_function ()
/#16 0x0000564c565ce959 in ?? ()

...
/#23856 0x00007f2e7b274ddb in swoole::PHPCoroutine::main_func (arg=0x7ffef2374260) at /tmp/swoole/ext-src/swoole_coroutine.cc:655
/#23857 0x00007f2e7b2f3a9d in std::function<void (void*)>::operator()(void*) const (__args#0=, this=0x564c58d442e0) at /usr/include/c++/9.3.0/bits/std_function.h:683
/#23858 swoole::coroutine::Context::context_func (arg=0x564c58d442e0) at /tmp/swoole/src/coroutine/context.cc:136
/#23859 0x00007f2e7b34ea71 in make_fcontext () at /tmp/swoole/thirdparty/boost/asm/make_x86_64_sysv_elf_gas.S:64
/#23860 0x0000000000000000 in ?? ()

(gdb) f 1
/#1 0x0000564c566ea17d in ?? ()
(gdb) f 0
/#0 0x0000564c566ea0ae in sapi_cli_single_write ()
(gdb)

发布于5年前 · 1 次浏览 · 来自提问

laofu360