<?xml version="1.0" encoding="utf-8"?>
<!--RSS generated by Flaimo.com RSS Builder [2026-11-19 20:34:43]-->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"><channel><docs>https://bugs.xdebug.org/</docs><link>https://bugs.xdebug.org/</link><description><![CDATA[MantisBT - Issues]]></description><title>MantisBT - Issues</title><image><title>MantisBT - Issues</title><url>https://bugs.xdebug.org/images/mantis_logo.png</url><link>https://bugs.xdebug.org/</link><description><![CDATA[MantisBT - Issues]]></description></image><language>en</language><category>All Projects</category><ttl>10</ttl><dc:language>en</dc:language><sy:updatePeriod>hourly</sy:updatePeriod><sy:updateFrequency>1</sy:updateFrequency><item><title>0002444: Swoole 6.1.13 / 6.2.6 + Xdebug 3.5.3  SIGSEGV（signal 11）</title><author></author><link>https://bugs.xdebug.org/view.php?id=2444</link><description><![CDATA[# 跟进 #6428：Swoole 6.1.13 / 6.2.6 + Xdebug 3.5.3 仍然 SIGSEGV（signal 11）&lt;br /&gt;
&lt;br /&gt;
跟进 &lt;a href=&quot;https://github.com/swoole/swoole-src/issues/6428&quot; rel=&quot;noopener,nofollow&quot;&gt;https://github.com/swoole/swoole-src/issues/6428&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
#6428 报的是 Swoole 5.1.4。维护者回复「更新到 6.1、6.2 版本，已兼容 xdebug」，并关闭了 issue。同一环境继续测了 **6.1 最新稳定版 6.1.13** 和 **6.2 最新稳定版 6.2.6**（PECL 上 6.3.0 仍是 RC1，没有测）。`swoole.enable_fiber_mock=On` 已经打开。两个版本在第一个 HTTP 请求上仍然是 signal 11，gdb 落点相同。&lt;br /&gt;
&lt;br /&gt;
## 结论&lt;br /&gt;
&lt;br /&gt;
崩溃不是 Linux 内核问题，也不是 boost fcontext 把 C 栈写坏。&lt;br /&gt;
&lt;br /&gt;
`Xdebug 3.5.3` 的 `xdebug_execute_user_code_end()` 在 observer `fcall_end` 里取函数栈顶。当时 Xdebug 的 per-fiber 栈 `count == 0`，`XDEBUG_VECTOR_TAIL()` 返回 NULL，下一行读 `fse-&gt;code_coverage_init` 空指针解引用，SIGSEGV。&lt;br /&gt;
&lt;br /&gt;
这条 observer 回调发生在 Swoole 协程里：`Swoole\Coroutine\Http\Server` 的 `onAccept`（内部函数）调用用户回调，用户回调里 `Swoole\Coroutine::create()` 再开一个协程。`enable_fiber_mock` 会把这次切换通知给 Xdebug，但通知发生时，外层用户帧已经压在另一条 Xdebug 栈上。切回来之后，当前栈是空的，用户函数返回就崩。&lt;br /&gt;
&lt;br /&gt;
6.1.13 和 6.2.6 的调用链一致，只是行号不同。&lt;br /&gt;
&lt;br /&gt;
## 环境&lt;br /&gt;
&lt;br /&gt;
| 项 | 值 |&lt;br /&gt;
| --- | --- |&lt;br /&gt;
| 宿主机 | Apple Silicon，Docker Desktop |&lt;br /&gt;
| 容器内核 | `Linux 7.0.14-linuxkit #1 SMP PREEMPT Fri Oct 30 13:45:20 UTC 2026 aarch64` |&lt;br /&gt;
| 发行版 | Debian GNU/Linux 13 (trixie) |&lt;br /&gt;
| PHP | 8.2.35 NTS，官方 `php:8.2.35-fpm` |&lt;br /&gt;
| GCC | 14.2.0 |&lt;br /&gt;
| Xdebug | 3.5.3，`mode=debug` |&lt;br /&gt;
| Swoole | 6.1.13（镜像内 pecl，Built Nov 18 2026 07:53:28），以及容器内源码编译的 6.2.6（Built Nov 18 2026 08:26:46） |&lt;br /&gt;
| 协程上下文 | boost asm context（`make_arm64_aapcs_elf_gas.S`） |&lt;br /&gt;
| OpenSSL | 6.2.6 的 `php --ri swoole` 显示 `OpenSSL 3.5.7 9 Jun 2026`，http2 / brotli / dtls 开启 |&lt;br /&gt;
&lt;br /&gt;
Zend 模块：Xdebug、Zend OPcache。&lt;br /&gt;
&lt;br /&gt;
### php.ini&lt;br /&gt;
&lt;br /&gt;
```ini&lt;br /&gt;
swoole.enable_fiber_mock = On&lt;br /&gt;
&lt;br /&gt;
zend_extension=xdebug&lt;br /&gt;
xdebug.mode=debug&lt;br /&gt;
xdebug.start_with_request=yes&lt;br /&gt;
xdebug.client_host=192.168.65.254&lt;br /&gt;
xdebug.client_port=9003&lt;br /&gt;
xdebug.idekey=PHPSTORM&lt;br /&gt;
xdebug.connect_timeout_ms=2000&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
6.2 已经没有 `swoole.enable_coroutine` 这个 ini。`php --ri swoole` 里和 fiber 相关的是：&lt;br /&gt;
&lt;br /&gt;
```text&lt;br /&gt;
swoole.enable_fiber_mock =&gt; On&lt;br /&gt;
coroutine =&gt; enabled with boost asm context&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
6.2.6 的 configure（与当时 6.1.13 的链接库对齐，brotli 开，其余 pecl 选项保持默认 no）：&lt;br /&gt;
&lt;br /&gt;
```text&lt;br /&gt;
./configure --with-php-config=/usr/local/bin/php-config \&lt;br /&gt;
  --enable-sockets=no --with-openssl-dir=no --enable-mysqlnd=no \&lt;br /&gt;
  --enable-swoole-curl=no --enable-cares=no --enable-brotli=yes \&lt;br /&gt;
  --with-brotli-dir=no --enable-zstd=no --enable-swoole-pgsql=no \&lt;br /&gt;
  --with-swoole-odbc=no --with-swoole-oracle=no --enable-swoole-sqlite=no \&lt;br /&gt;
  --with-swoole-firebird=no --enable-swoole-thread=no --enable-iouring=no \&lt;br /&gt;
  --with-liburing-dir=no --enable-uring-socket=no --with-swoole-ssh2=no \&lt;br /&gt;
  --enable-swoole-ftp=no&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
`php --ri` 仍显示 openssl / http2 / dtls / brotli 为 enabled。&lt;br /&gt;
&lt;br /&gt;
## 最小复现（6.2.6 上已跑通）&lt;br /&gt;
&lt;br /&gt;
不需要 ThinkPHP。Xdebug 模式用环境变量打开，避免 ini 里的 `XDEBUG_MODE` 把模式关掉。IDE 不需要真的连上：`client_port=9`，连接失败即可。&lt;br /&gt;
&lt;br /&gt;
```php&lt;br /&gt;
&lt;?php&lt;br /&gt;
use Swoole\Coroutine;&lt;br /&gt;
use Swoole\Coroutine\Http\Server;&lt;br /&gt;
use Swoole\Http\Request;&lt;br /&gt;
use Swoole\Http\Response;&lt;br /&gt;
&lt;br /&gt;
class App {&lt;br /&gt;
    public function onRequest(Response $res): void&lt;br /&gt;
    {&lt;br /&gt;
        Coroutine::create(function () use ($res) {&lt;br /&gt;
            Coroutine::sleep(0.05);&lt;br /&gt;
            $res-&gt;end(&quot;ok&quot;);&lt;br /&gt;
        });&lt;br /&gt;
    }&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Coroutine\run(function () {&lt;br /&gt;
    $app = new App();&lt;br /&gt;
    $server = new Server(&quot;127.0.0.1&quot;, 19502, false, true);&lt;br /&gt;
    $server-&gt;handle(&quot;/&quot;, function (Request $req, Response $res) use ($app) {&lt;br /&gt;
        $app-&gt;onRequest($res);&lt;br /&gt;
    });&lt;br /&gt;
    $server-&gt;start();&lt;br /&gt;
});&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
```bash&lt;br /&gt;
XDEBUG_MODE=debug php \&lt;br /&gt;
  -d xdebug.start_with_request=yes \&lt;br /&gt;
  -d xdebug.client_host=127.0.0.1 \&lt;br /&gt;
  -d xdebug.client_port=9 \&lt;br /&gt;
  -d xdebug.connect_timeout_ms=200 \&lt;br /&gt;
  repro.php&lt;br /&gt;
&lt;br /&gt;
curl -v &lt;a href=&quot;http://127.0.0.1:19502/&quot; rel=&quot;noopener,nofollow&quot;&gt;http://127.0.0.1:19502/&lt;/a&gt;&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
结果：`curl: (52) Empty reply from server`。PHP 进程直接死掉，没有 Swoole 的 “A process crash occurred” 文本（单进程，不是 ProcessPool worker）。core 的信号是 SIGSEGV，栈和下面业务进程一致，正在返回的函数就是 `onRequest`，Xdebug 栈 `count=0`。&lt;br /&gt;
&lt;br /&gt;
对照：同样的 Server，handle 闭包里直接 `Coroutine::create()` 并立刻 `$res-&gt;end(&quot;ok&quot;)`，且 `xdebug.start_with_request=no`，请求返回 `HTTP 200` / body `ok`，不崩。也就是说，只加载 Xdebug、或者子协程不让出，不一定崩；**调试器启动（`start_with_request=yes`）加上「用户方法里 `Coroutine::create()`，子协程里 `Coroutine::sleep()`」会崩。**&lt;br /&gt;
&lt;br /&gt;
## 业务侧同样的路径&lt;br /&gt;
&lt;br /&gt;
ThinkPHP `topthink/think-swoole` 的 HTTP worker 就是这个结构。每个 worker 跑 `Swoole\Coroutine\Http\Server`，handle 闭包再调用 `onRequest()`，`onRequest()` 里 `Coroutine::create()`：&lt;br /&gt;
&lt;br /&gt;
```php&lt;br /&gt;
// vendor/topthink/think-swoole/src/concerns/InteractsWithHttp.php&lt;br /&gt;
$server = new Server($host, $port, false, true);&lt;br /&gt;
$server-&gt;handle('/', function (Request $req, Response $res) {&lt;br /&gt;
    if ($this-&gt;wsEnable &amp;&amp; $this-&gt;isWebsocketRequest($req)) {&lt;br /&gt;
        $this-&gt;onHandShake($req, $res);&lt;br /&gt;
    } else {&lt;br /&gt;
        $this-&gt;onRequest($req, $res);   // 第 51 行，opcode ZEND_DO_FCALL&lt;br /&gt;
    }&lt;br /&gt;
});&lt;br /&gt;
&lt;br /&gt;
public function onRequest($req, $res)&lt;br /&gt;
{&lt;br /&gt;
    Coroutine::create(function () use ($req, $res) {&lt;br /&gt;
        $this-&gt;runInSandbox(function (...) use ($req, $res) {&lt;br /&gt;
            // 真正的 HTTP 处理&lt;br /&gt;
        });&lt;br /&gt;
    });&lt;br /&gt;
}   // 崩溃时 opline 在第 141 行，函数正在返回&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
worker 数是 `swoole_cpu_num()`。请求：&lt;br /&gt;
&lt;br /&gt;
```bash&lt;br /&gt;
curl &lt;a href=&quot;http://127.0.0.1:9501/adminapi/setting/config/getAdminBase&quot; rel=&quot;noopener,nofollow&quot;&gt;http://127.0.0.1:9501/adminapi/setting/config/getAdminBase&lt;/a&gt;&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
不加载 Xdebug 时，这条请求正常返回业务的 HTTP 401（未带 JWT）。加载 Xdebug 后连接被重置。&lt;br /&gt;
&lt;br /&gt;
## 6.1.13&lt;br /&gt;
&lt;br /&gt;
```text&lt;br /&gt;
[2026-11-18 08:04:04 &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=7&quot;&gt;0000007&lt;/a&gt;.0]  WARNING  Worker::report_error(): worker(pid=14, id=6) abnormal exit, status=0, signal=11&lt;br /&gt;
A process crash occurred in Swoole-v6.1.13. Please report this issue.&lt;br /&gt;
&lt;br /&gt;
OS: Linux 7.0.14-linuxkit #1 SMP PREEMPT Fri Oct 30 13:45:20 UTC 2026 aarch64&lt;br /&gt;
GCC_VERSION: 14.2.0&lt;br /&gt;
PHP_VERSION : 8.2.35&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
`curl`：`Empty reply from server`。core：`/buffhub/public/core`，133MB，`swoole: http server &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=6&quot;&gt;0000006&lt;/a&gt;`。&lt;br /&gt;
&lt;br /&gt;
## 6.2.6&lt;br /&gt;
&lt;br /&gt;
替换 `swoole.so` 并重启 worker 后再打同一条请求：&lt;br /&gt;
&lt;br /&gt;
```text&lt;br /&gt;
[2026-11-18 08:27:40 #52333.0]  WARNING  Worker::report_error(): worker(pid=52340, id=6) abnormal exit, status=0, signal=11&lt;br /&gt;
A process crash occurred in Swoole-v6.2.6. Please report this issue.&lt;br /&gt;
&lt;br /&gt;
OS: Linux 7.0.14-linuxkit #1 SMP PREEMPT Fri Oct 30 13:45:20 UTC 2026 aarch64&lt;br /&gt;
GCC_VERSION: 14.2.0&lt;br /&gt;
OPENSSL_VERSION: OpenSSL 3.5.7 9 Jun 2026&lt;br /&gt;
PHP_VERSION : 8.2.35&lt;br /&gt;
&lt;br /&gt;
[2026-11-18 08:27:41 #52333.0]  WARNING  Worker::report_error(): worker(pid=52341, id=7) abnormal exit, status=0, signal=11&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
连续两次请求打挂两个 worker。core 135MB。&lt;br /&gt;
&lt;br /&gt;
## gdb&lt;br /&gt;
&lt;br /&gt;
两份 core 都用 gdb 16.3 看过。扩展带 debug info，未 strip。PHP 本身是 NTS non-debug。&lt;br /&gt;
&lt;br /&gt;
### 6.2.6（业务 worker，以及上面的最小脚本，栈相同）&lt;br /&gt;
&lt;br /&gt;
```text&lt;br /&gt;
Program terminated with signal SIGSEGV, Segmentation fault.&lt;br /&gt;
#0  xdebug_execute_user_code_end (execute_data=0xffff9ff78240, retval=0xaaaad6497118)&lt;br /&gt;
      at xdebug/src/base/base.c:811&lt;br /&gt;
#1  xdebug_execute_end                                      base.c:1053&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=2&quot;&gt;0000002&lt;/a&gt;  zend_observer_fcall_end&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=3&quot;&gt;0000003&lt;/a&gt;  execute_ex&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=6&quot;&gt;0000006&lt;/a&gt;  zend_call_function&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=7&quot;&gt;0000007&lt;/a&gt;  sw_zend_call_function_ex                                php_swoole_private.h:915&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=8&quot;&gt;0000008&lt;/a&gt;  zend::function::call                                    php_swoole_cxx.cc:111&lt;br /&gt;
      enable_coroutine=false, argc=2&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=10&quot;&gt;0000010&lt;/a&gt; zim_swoole_http_server_coro_onAccept                    swoole_http_server_coro.cc:701&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=12&quot;&gt;0000012&lt;/a&gt; swoole::PHPCoroutine::main_func                         swoole_coroutine.cc:796&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=14&quot;&gt;0000014&lt;/a&gt; swoole::coroutine::Context::context_func                src/coroutine/context.cc:149&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=15&quot;&gt;0000015&lt;/a&gt; swoole_make_fcontext                                    thirdparty/boost/asm/make_arm64_aapcs_elf_gas.S:94&lt;br /&gt;
Backtrace stopped: previous frame identical to this frame (corrupt stack?)&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
`&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=15&quot;&gt;0000015&lt;/a&gt;` 那句 `corrupt stack?` 是 gdb 无法展开 boost fcontext 的汇编帧。崩溃指令的 `sp` 是正常的，见下面寄存器。不是栈被写坏。&lt;br /&gt;
&lt;br /&gt;
### 6.1.13（同一请求）&lt;br /&gt;
&lt;br /&gt;
行号不同，函数相同：&lt;br /&gt;
&lt;br /&gt;
```text&lt;br /&gt;
#0  xdebug_execute_user_code_end                            base.c:811&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=7&quot;&gt;0000007&lt;/a&gt;  sw_zend_call_function_ex                                php_swoole_private.h:909&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=8&quot;&gt;0000008&lt;/a&gt;  zend::function::call                                    php_swoole_cxx.cc:111&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=10&quot;&gt;0000010&lt;/a&gt; zim_swoole_http_server_coro_onAccept                    swoole_http_server_coro.cc:703&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=12&quot;&gt;0000012&lt;/a&gt; swoole::PHPCoroutine::main_func                         swoole_coroutine.cc:778&lt;br /&gt;
&lt;a href=&quot;https://bugs.xdebug.org/view.php?id=15&quot;&gt;0000015&lt;/a&gt; swoole_make_fcontext                                    make_arm64_aapcs_elf_gas.S:94&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
5.1.4（#6428 里那份 core）也是这条链：`onAccept` → `PHPCoroutine::main_func` → `swoole_make_fcontext`，死在 `xdebug_execute_user_code_end`。&lt;br /&gt;
&lt;br /&gt;
### 正在返回的 PHP 帧（6.1.13 与 6.2.6 一致）&lt;br /&gt;
&lt;br /&gt;
| 帧 | 函数 | 位置 |&lt;br /&gt;
| --- | --- | --- |&lt;br /&gt;
| 当前 | `onRequest` | `InteractsWithHttp.php:141` |&lt;br /&gt;
| prev | `think\swoole\concerns\{closure}` | 同文件第 51 行，opcode `ZEND_DO_FCALL`（60） |&lt;br /&gt;
| prev2 | 内部函数 `onAccept` | 无 filename |&lt;br /&gt;
&lt;br /&gt;
最小脚本的 core 里，当前函数名同样是 `onRequest`。&lt;br /&gt;
&lt;br /&gt;
### 出错指令&lt;br /&gt;
&lt;br /&gt;
`xdebug_execute_user_code_end+76`：&lt;br /&gt;
&lt;br /&gt;
```asm&lt;br /&gt;
ldrb w0, [x19, &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=95&quot;&gt;0000095&lt;/a&gt;]     ; x19 == 0&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
6.2.6 业务 core 和最小脚本 core 都是：&lt;br /&gt;
&lt;br /&gt;
```text&lt;br /&gt;
x19 = 0&lt;br /&gt;
XG_BASE(stack) count = 0&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
6.1.13 业务 core 额外看过 vector 内容：&lt;br /&gt;
&lt;br /&gt;
```text&lt;br /&gt;
vector = 0xaaaacfdaea80&lt;br /&gt;
count  = 0&lt;br /&gt;
element size = 240&lt;br /&gt;
data   = 0xaaaacfba2fa0&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
`x19` 是 `function_stack_entry *fse`。反汇编对应 `vector.h` 的 `XDEBUG_VECTOR_TAIL`：`count == 0` 时走 `mov x19, #0`。随后的 `ldrb` 是在读 `fse-&gt;code_coverage_init`（该字段在结构体偏移 95）。故障地址是 `0x5f`，不是一个被破坏的堆指针。&lt;br /&gt;
&lt;br /&gt;
gdb 把这条指令标在 `base.c:811`，是编译器把 809–811 行收成了一条空指针加载。源码如下（Xdebug 3.5.3 `src/base/base.c`）：&lt;br /&gt;
&lt;br /&gt;
```c&lt;br /&gt;
static void xdebug_execute_user_code_end(zend_execute_data *execute_data, zval *retval)&lt;br /&gt;
{&lt;br /&gt;
    zend_op_array *op_array = &amp;(execute_data-&gt;func-&gt;op_array);&lt;br /&gt;
    function_stack_entry *fse;&lt;br /&gt;
&lt;br /&gt;
    fse = XDEBUG_VECTOR_TAIL(XG_BASE(stack));   /* count == 0 时为 NULL */&lt;br /&gt;
&lt;br /&gt;
    if (XDEBUG_MODE_IS(XDEBUG_MODE_PROFILING)) {&lt;br /&gt;
        xdebug_profiler_execute_ex_end(fse);&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
    if (fse-&gt;code_coverage_init) {              /* 这里 SIGSEGV */&lt;br /&gt;
        xdebug_coverage_execute_ex_end(fse, op_array, ...);&lt;br /&gt;
    }&lt;br /&gt;
    ...&lt;br /&gt;
}&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
调用方 `xdebug_execute_end()` 只判断了栈对象非空，没有判断栈深度：&lt;br /&gt;
&lt;br /&gt;
```c&lt;br /&gt;
static void xdebug_execute_end(zend_execute_data *execute_data, zval *retval)&lt;br /&gt;
{&lt;br /&gt;
    if (!XG_BASE(stack)) {&lt;br /&gt;
        return;&lt;br /&gt;
    }&lt;br /&gt;
    if (should_run_user_handler(execute_data)) {&lt;br /&gt;
        xdebug_execute_user_code_end(execute_data, retval);&lt;br /&gt;
    }&lt;br /&gt;
}&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
`onRequest` 是普通用户方法，`should_run_user_handler()` 为 true，所以一定会走进去。`fcall_begin` 时压进去的那一帧不在这条 `count == 0` 的栈上。&lt;br /&gt;
&lt;br /&gt;
## Swoole 6.2.6 里和这次栈切换对应的代码&lt;br /&gt;
&lt;br /&gt;
`ext-src/swoole_coroutine.cc`。&lt;br /&gt;
&lt;br /&gt;
协程入口只有在入口函数是用户函数时才通知 fiber observer。`Coroutine\Http\Server` 的 accept 协程入口是内部函数 `onAccept`（`zim_swoole_http_server_coro_onAccept`），这个分支不会走：&lt;br /&gt;
&lt;br /&gt;
```cpp&lt;br /&gt;
void PHPCoroutine::main_func(void *_args) {&lt;br /&gt;
    ...&lt;br /&gt;
    if (UNEXPECTED(ctx-&gt;fiber_context &amp;&amp; ctx-&gt;fci_cache.function_handler-&gt;type == ZEND_USER_FUNCTION)) {&lt;br /&gt;
        zend_execute_data *tmp = EG(current_execute_data);&lt;br /&gt;
        zend_execute_data call = {};&lt;br /&gt;
        EG(current_execute_data) = &call;&lt;br /&gt;
        EG(current_execute_data)-&gt;opline = ctx-&gt;fci_cache.function_handler-&gt;op_array.opcodes;&lt;br /&gt;
        call.func = ctx-&gt;fci_cache.function_handler;&lt;br /&gt;
        fiber_context_switch_try_notify(get_origin_context(ctx), ctx);&lt;br /&gt;
        EG(current_execute_data) = tmp;&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
    zend_call_function(&amp;ctx-&gt;fci, &amp;ctx-&gt;fci_cache);   /* 796 行，崩溃栈在这之下 */&lt;br /&gt;
    ...&lt;br /&gt;
}&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
gdb 里 `onAccept` 调用用户回调时 `enable_coroutine=false`。也就是说 handle 闭包和 `onRequest()` 跑在 accept 协程里面，不是再包一层协程。Xdebug 的 `fcall_begin` 把 `onRequest` 压进**当时**的 `XG_BASE(stack)`。&lt;br /&gt;
&lt;br /&gt;
随后 `onRequest()` 里的 `Coroutine::create()` 才会进入一个用户函数协程。那个协程的 `main_func` 会调用 `fiber_context_switch_try_notify()`。第一次通知时，目标 fiber 的 status 被强制改成 `INIT`：&lt;br /&gt;
&lt;br /&gt;
```cpp&lt;br /&gt;
void PHPCoroutine::fiber_context_switch_notify(const PHPContext *from, PHPContext *to) {&lt;br /&gt;
    zend_fiber_context *from_context = from-&gt;fiber_context;&lt;br /&gt;
    zend_fiber_context *to_context = to-&gt;fiber_context;&lt;br /&gt;
&lt;br /&gt;
    from_context-&gt;status = fiber_get_status(from);&lt;br /&gt;
    to_context-&gt;status = fiber_get_status(to);&lt;br /&gt;
&lt;br /&gt;
    if (!to-&gt;fiber_init_notified) {&lt;br /&gt;
        to_context-&gt;status = ZEND_FIBER_STATUS_INIT;&lt;br /&gt;
        zend_observer_fiber_switch_notify(from_context, to_context);&lt;br /&gt;
        to_context-&gt;status = fiber_get_status(to);&lt;br /&gt;
        to-&gt;fiber_init_notified = true;&lt;br /&gt;
    } else {&lt;br /&gt;
        zend_observer_fiber_switch_notify(from_context, to_context);&lt;br /&gt;
    }&lt;br /&gt;
}&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
Xdebug 3.5.3 `xdebug_fiber_switch_observer()` 看到 `to-&gt;status == ZEND_FIBER_STATUS_INIT` 就**新建一条空的函数栈**，替换 `XG_BASE(stack)`，再压一个伪造的 fiber 帧：&lt;br /&gt;
&lt;br /&gt;
```c&lt;br /&gt;
if (to-&gt;status == ZEND_FIBER_STATUS_INIT) {&lt;br /&gt;
    current_stack = create_stack_for_fiber(to_key, to);&lt;br /&gt;
} else {&lt;br /&gt;
    current_stack = find_stack_for_fiber(to_key, to);&lt;br /&gt;
}&lt;br /&gt;
XG_BASE(stack) = current_stack;&lt;br /&gt;
&lt;br /&gt;
if (to-&gt;status == ZEND_FIBER_STATUS_INIT) {&lt;br /&gt;
    add_fiber_main(to_key, to);&lt;br /&gt;
}&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
它不会把切走之前那条栈（上面有 `onRequest` 的帧）保存回 `from` 的 fiber。accept 协程因为入口是内部函数，之前也没有作为 `to` 被登记过。子协程 `sleep` 让出再切回来时，当前 Xdebug 栈已经不是 `fcall_begin` 用的那条。`onRequest` 返回时 `count == 0`，`fcall_end` 空指针。&lt;br /&gt;
&lt;br /&gt;
6.1.13 的 `fiber_context_switch_notify` 反汇编是同一段逻辑：第一次切入时 `str wzr, [fiber+40]` 把 status 写成 0，再 `bl zend_observer_fiber_switch_notify`。&lt;br /&gt;
&lt;br /&gt;
## 期望&lt;br /&gt;
&lt;br /&gt;
`swoole.enable_fiber_mock=On` 时，上面的最小脚本和 ThinkPHP 的 `Coroutine\Http\Server` 请求都不要 SIGSEGV。Xdebug 可以连上调试器，也可以只是 `start_with_request=yes` 但客户端连不上。&lt;br /&gt;
&lt;br /&gt;
不加载 Xdebug 时，同一条业务请求返回 HTTP 401，进程不退出。&lt;br /&gt;
&lt;br /&gt;
## 实际&lt;br /&gt;
&lt;br /&gt;
| 版本 | `enable_fiber_mock` | 结果 |&lt;br /&gt;
| --- | --- | --- |&lt;br /&gt;
| 5.1.4（#6428） | On | signal 11，`xdebug_execute_user_code_end` |&lt;br /&gt;
| 6.1.13 | On | 同样 |&lt;br /&gt;
| 6.2.6 | On | 同样，最小脚本也能复现 |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
以下是经过修复的补丁&lt;br /&gt;
xdebug-3.5.3-empty-stack.patch&lt;br /&gt;
--- a/src/base/base.c&lt;br /&gt;
+++ b/src/base/base.c&lt;br /&gt;
@@ -803,6 +803,11 @@&lt;br /&gt;
 	function_stack_entry *fse;&lt;br /&gt;
 &lt;br /&gt;
 	fse = XDEBUG_VECTOR_TAIL(XG_BASE(stack));&lt;br /&gt;
+	/* TAIL is NULL when the fiber stack has no frames. A coroutine library can&lt;br /&gt;
+	 * deliver fcall_end against that stack; dereferencing fse is a SIGSEGV. */&lt;br /&gt;
+	if (!fse) {&lt;br /&gt;
+		return;&lt;br /&gt;
+	}&lt;br /&gt;
 &lt;br /&gt;
 	if (XDEBUG_MODE_IS(XDEBUG_MODE_PROFILING)) {&lt;br /&gt;
 		xdebug_profiler_execute_ex_end(fse);&lt;br /&gt;
@@ -976,6 +981,9 @@&lt;br /&gt;
 	/* Re-acquire the tail as nested calls through&lt;br /&gt;
 	 * xdebug_old_execute_internal() might have reallocated the vector */&lt;br /&gt;
 	fse = XDEBUG_VECTOR_TAIL(XG_BASE(stack));&lt;br /&gt;
+	if (!fse) {&lt;br /&gt;
+		return;&lt;br /&gt;
+	}&lt;br /&gt;
 &lt;br /&gt;
 	if (XDEBUG_MODE_IS(XDEBUG_MODE_PROFILING)) {&lt;br /&gt;
 		xdebug_profiler_execute_internal_end(fse);&lt;br /&gt;
@@ -1150,7 +1158,13 @@&lt;br /&gt;
 	tmp-&gt;function.object_class = NULL;&lt;br /&gt;
 	tmp-&gt;function.scope_class = NULL;&lt;br /&gt;
 	tmp-&gt;function.function = zend_string_copy(fiber_key);&lt;br /&gt;
-	tmp-&gt;filename = zend_string_copy(zend_get_executed_filename_ex());&lt;br /&gt;
+	/* Internal coroutine entries have no user frame, so the filename is NULL.&lt;br /&gt;
+	 * zend_string_copy() would dereference it. The stack-entry dtor already&lt;br /&gt;
+	 * allows a NULL filename. */&lt;br /&gt;
+	{&lt;br /&gt;
+		zend_string *filename = zend_get_executed_filename_ex();&lt;br /&gt;
+		tmp-&gt;filename = filename ? zend_string_copy(filename) : NULL;&lt;br /&gt;
+	}&lt;br /&gt;
 	tmp-&gt;lineno = zend_get_executed_lineno();&lt;br /&gt;
 &lt;br /&gt;
 	tmp-&gt;prev_memory = XG_BASE(prev_memory);]]></description><category>Code Coverage</category><pubDate>Thu, 19 Nov 2026 02:31:00 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2444</guid><comments>https://bugs.xdebug.org/view.php?id=2444#bugnotes</comments></item><item><title>0002443: Array items are transformed into references during exceptions handling</title><author></author><link>https://bugs.xdebug.org/view.php?id=2443</link><description><![CDATA[With xdebug (develop mode) enabled the script in 'Steps to Reproduce' gives another output than with xdebug off. The product version field does not allow me to select xdebug 3.5.3, but this is in 3.5.3. I verified this in PHP 8.4.24 and PHP 8.4.26.&lt;br /&gt;
&lt;br /&gt;
What seems to happen:&lt;br /&gt;
When an reference exists to an item in an array, during exception handling that array item is then transformed into a reference itself. It looks like this is not specific for array items, but is exposed easier in the array context because of the way array copying works.&lt;br /&gt;
&lt;br /&gt;
I encountered this issue in a real world application where my tests would fail with xdebug on and would pass with xdebug off.]]></description><category>Uncategorized</category><pubDate>Sat, 24 Oct 2026 09:07:08 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2443</guid><comments>https://bugs.xdebug.org/view.php?id=2443#bugnotes</comments></item><item><title>0002442: SIGSEGV crash in xdebug_hash_destroy from xdebug_debugger_post_deactivate in xdebug 3.5.3 and PHP 8.3.36</title><author></author><link>https://bugs.xdebug.org/view.php?id=2442</link><description><![CDATA[Hi,&lt;br /&gt;
&lt;br /&gt;
I'm running this project to scan for the php2shell vulnerabilities &lt;a href=&quot;https://github.com/assetnote/php2shell-scanner&quot; rel=&quot;noopener,nofollow&quot;&gt;https://github.com/assetnote/php2shell-scanner&lt;/a&gt; and it's currently causing error 500s on patched servers (such as mod_php 8.3.36). However, on a server with xdebug 3.5.3, it causes a segfault.&lt;br /&gt;
&lt;br /&gt;
Here's the stack trace:&lt;br /&gt;
&lt;br /&gt;
coredumpctl info&lt;br /&gt;
           PID: 641891 (httpd-prefork)&lt;br /&gt;
           UID: 30 (wwwrun)&lt;br /&gt;
           GID: 8 (www)&lt;br /&gt;
        Signal: 11 (SEGV)&lt;br /&gt;
     Timestamp: Thu 2026-10-22 00:35:58 PDT (13s ago)&lt;br /&gt;
  Command Line: /usr/sbin/httpd-prefork -DSYSCONFIG -DSSL -DSTATUS -DEXTENDED_STATUS -C $'PidFile /run/httpd.pid' -C $'Include /etc/apache2/sysconfig.d//loadmodule.conf' -C &gt;&lt;br /&gt;
    Executable: /usr/sbin/httpd-prefork&lt;br /&gt;
 Control Group: /system.slice/apache2.service&lt;br /&gt;
          Unit: apache2.service&lt;br /&gt;
         Slice: system.slice&lt;br /&gt;
       Boot ID: ******&lt;br /&gt;
    Machine ID: ******&lt;br /&gt;
      Hostname: ******&lt;br /&gt;
       Storage: /var/lib/systemd/coredump/core.httpd-prefork.30.7ed6e01e97214b66ad7c4b6cc9bc673b.641891.1792654558000000.zst (present)&lt;br /&gt;
  Size on Disk: 39.4M&lt;br /&gt;
       Message: Process 641891 (httpd-prefork) of user 30 dumped core.&lt;br /&gt;
                &lt;br /&gt;
                Stack trace of thread 641891:&lt;br /&gt;
                #0  0x00007fe1638a6aa4 xdebug_hash_destroy (xdebug.so + 0x1eaa4)&lt;br /&gt;
                #1  0x00007fe1638bcdfc xdebug_debugger_post_deactivate (xdebug.so + 0x34dfc)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=2&quot;&gt;0000002&lt;/a&gt;  0x00007fe16389fb20 zm_post_zend_deactivate_xdebug (xdebug.so + 0x17b20)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=3&quot;&gt;0000003&lt;/a&gt;  0x00007fe1640ce786 zend_post_deactivate_modules (mod_php8.so + 0x2ce786)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=4&quot;&gt;0000004&lt;/a&gt;  0x00007fe164053036 php_request_shutdown (mod_php8.so + 0x253036)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=5&quot;&gt;0000005&lt;/a&gt;  0x00007fe1641bd227 n/a (mod_php8.so + 0x3bd227)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=6&quot;&gt;0000006&lt;/a&gt;  0x00005641a691a340 ap_run_handler (/usr/sbin/httpd-prefork + 0x60340)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=7&quot;&gt;0000007&lt;/a&gt;  0x00005641a691dec6 ap_invoke_handler (/usr/sbin/httpd-prefork + 0x63ec6)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=8&quot;&gt;0000008&lt;/a&gt;  0x00005641a69442e5 ap_process_async_request (/usr/sbin/httpd-prefork + 0x8a2e5)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=9&quot;&gt;0000009&lt;/a&gt;  0x00005641a694450f ap_process_request (/usr/sbin/httpd-prefork + 0x8a50f)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=10&quot;&gt;0000010&lt;/a&gt; 0x00005641a694487b ap_process_http_sync_connection (/usr/sbin/httpd-prefork + 0x8a87b)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=11&quot;&gt;0000011&lt;/a&gt; 0x00005641a6930200 ap_run_process_connection (/usr/sbin/httpd-prefork + 0x76200)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=12&quot;&gt;0000012&lt;/a&gt; 0x00005641a6947ee9 child_main (/usr/sbin/httpd-prefork + 0x8dee9)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=13&quot;&gt;0000013&lt;/a&gt; 0x00005641a6948364 make_child (/usr/sbin/httpd-prefork + 0x8e364)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=14&quot;&gt;0000014&lt;/a&gt; 0x00005641a69483b1 startup_children (/usr/sbin/httpd-prefork + 0x8e3b1)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=15&quot;&gt;0000015&lt;/a&gt; 0x00005641a6949cf3 prefork_run (/usr/sbin/httpd-prefork + 0x8fcf3)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=16&quot;&gt;0000016&lt;/a&gt; 0x00005641a68fafc0 ap_run_mpm (/usr/sbin/httpd-prefork + 0x40fc0)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=17&quot;&gt;0000017&lt;/a&gt; 0x00005641a68fa32c main (/usr/sbin/httpd-prefork + 0x4032c)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=18&quot;&gt;0000018&lt;/a&gt; 0x00007fe165647340 __libc_start_call_main (libc.so.6 + 0x2a340)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=19&quot;&gt;0000019&lt;/a&gt; 0x00007fe165647409 __libc_start_main_impl (libc.so.6 + 0x2a409)&lt;br /&gt;
                &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=20&quot;&gt;0000020&lt;/a&gt; 0x00005641a68fa455 _start (/usr/sbin/httpd-prefork + 0x40455)&lt;br /&gt;
                ELF object binary architecture: AMD x86-64]]></description><category>Stacktraces</category><pubDate>Thu, 22 Oct 2026 07:54:39 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2442</guid><comments>https://bugs.xdebug.org/view.php?id=2442#bugnotes</comments></item><item><title>0002441: var_export() with min() gives different answers, depending on whether Xdebug is on or off</title><author></author><link>https://bugs.xdebug.org/view.php?id=2441</link><description><![CDATA[With Xdebug on, `var_export(min(0,null));`, produces `0`, and with it off, it produces `NULL`.]]></description><category>Uncategorized</category><pubDate>Thu, 08 Oct 2026 16:31:50 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2441</guid><comments>https://bugs.xdebug.org/view.php?id=2441#bugnotes</comments></item><item><title>0002440: With UNUSED | DEAD_CODE | BRANCH_CHECK together, each call costs more the more calls the process has already made; stopping cove</title><author></author><link>https://bugs.xdebug.org/view.php?id=2440</link><description><![CDATA[Xdebug version: 3.5.3, which is not yet listed under Product Version. Also reproduced on 3.4.0.&lt;br /&gt;
&lt;br /&gt;
When code coverage is started with XDEBUG_CC_UNUSED | XDEBUG_CC_DEAD_CODE | XDEBUG_CC_BRANCH_CHECK, every call to a measured function costs more the more such calls the process has already made. xdebug_stop_code_coverage() (default cleanup) does not reset this, and neither does starting coverage again.&lt;br /&gt;
&lt;br /&gt;
The three flags have to be used together. BRANCH_CHECK on its own, and every pair of the three flags, stays flat (see Additional Information).&lt;br /&gt;
&lt;br /&gt;
Expected result:&lt;br /&gt;
The time per round of the script below stays roughly the same over all rounds, as it does with any two of the three flags. Branch checking may make each round slower, but a round should not become slower because earlier rounds ran.&lt;br /&gt;
&lt;br /&gt;
Actual result (Xdebug 3.5.3, ms per round, every round does the same work):&lt;br /&gt;
&lt;br /&gt;
  repro.php lines (UNUSED | DEAD_CODE):&lt;br /&gt;
    round  50:     3.06 ms&lt;br /&gt;
    round 100:     3.55 ms&lt;br /&gt;
    round 150:     3.47 ms&lt;br /&gt;
    round 200:     3.53 ms&lt;br /&gt;
&lt;br /&gt;
  repro.php (UNUSED | DEAD_CODE | BRANCH_CHECK):&lt;br /&gt;
    round  50:    47.15 ms&lt;br /&gt;
    round 100:   163.77 ms&lt;br /&gt;
    round 150:   387.12 ms&lt;br /&gt;
    round 200:   643.29 ms&lt;br /&gt;
&lt;br /&gt;
A second run gave 67.85 / 167.60 / 378.58 / 586.65 ms. Xdebug 3.4.0 on the same machine gives 35.76 / 129.18 / 359.04 / 599.47 ms.]]></description><category>Code Coverage</category><pubDate>Wed, 07 Oct 2026 14:31:00 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2440</guid><comments>https://bugs.xdebug.org/view.php?id=2440#bugnotes</comments></item><item><title>0002438: XDEBUG_CC_UNUSED no longer reports lines of unexecuted functions in files compiled before xdebug_start_code_coverage()</title><author></author><link>https://bugs.xdebug.org/view.php?id=2438</link><description><![CDATA[With Xdebug 3.6.0alpha1, xdebug_get_code_coverage() no longer reports lines of functions (methods) that were not executed when the file declaring them was compiled before xdebug_start_code_coverage(XDEBUG_CC_UNUSED) was called. Such lines are reported with -1 by Xdebug 3.5.3 (current stable), and they are still reported by 3.6.0alpha1 when the file is compiled after code coverage was started.&lt;br /&gt;
&lt;br /&gt;
This affects PHPUnit / php-code-coverage: unexecuted lines disappear from the coverage data instead of being reported as &quot;not executed&quot;. This was found because phpcov's test suite started to fail in CI once setup-php installed Xdebug 3.6.0alpha1.]]></description><category>Code Coverage</category><pubDate>Thu, 01 Oct 2026 06:47:13 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2438</guid><comments>https://bugs.xdebug.org/view.php?id=2438#bugnotes</comments></item><item><title>0002252: Running phpunit in coverage triggers segfault in xdebug_branch_info_mark_reached</title><author></author><link>https://bugs.xdebug.org/view.php?id=2252</link><description><![CDATA[When using php 8.2.17 and xdebug 3.3.1 on phpunit 9 coverage test triggers a segfault]]></description><category>Code Coverage</category><pubDate>Wed, 29 Jul 2026 13:23:08 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2252</guid><comments>https://bugs.xdebug.org/view.php?id=2252#bugnotes</comments></item><item><title>0002434: Version 3.5.3, test failure on aarch64</title><author></author><link>https://bugs.xdebug.org/view.php?id=2434</link><description><![CDATA[Building version 3.5.3 and running the test suite&lt;br /&gt;
&lt;br /&gt;
FAILED TEST SUMMARY&lt;br /&gt;
---------------------------------------------------------------------&lt;br /&gt;
Test for bug &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=2424&quot;&gt;0002424&lt;/a&gt;: Ctrl Socket: Aliveness after empty command [tests/debugger/bug02424-01.phpt]&lt;br /&gt;
Test for bug &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=2424&quot;&gt;0002424&lt;/a&gt;: Ctrl Socket: Command that doesn't exist [tests/debugger/bug02424-02.phpt]&lt;br /&gt;
Test for bug &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=2424&quot;&gt;0002424&lt;/a&gt;: Ctrl Socket: 'ps' command [tests/debugger/bug02424-03.phpt]&lt;br /&gt;
Test for bug &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=2424&quot;&gt;0002424&lt;/a&gt;: Ctrl Socket: Invalid command arguments [tests/debugger/bug02424-04.phpt]&lt;br /&gt;
&lt;br /&gt;
All failing with &lt;br /&gt;
001+ PHP Warning:  stream_socket_client(): Unable to connect to unix://\0xdebug-ctrl.32289 (Connection refused) in /tmp/11-bug02424-03 on line 3&lt;br /&gt;
002+ PHP Fatal error:  Uncaught TypeError: stream_set_write_buffer(): Argument #1 ($stream) must be of type resource, false given in /tmp/11-bug02424-03:4&lt;br /&gt;
&lt;br /&gt;
No problem on x86_64&lt;br /&gt;
&lt;br /&gt;
May be a issue in PHP.]]></description><category>Uncategorized</category><pubDate>Tue, 09 Jun 2026 09:13:25 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2434</guid><comments>https://bugs.xdebug.org/view.php?id=2434#bugnotes</comments></item><item><title>0002413: Suggestion: Develop mode in terminal</title><author></author><link>https://bugs.xdebug.org/view.php?id=2413</link><description><![CDATA[Suggestion to not display html tags in develop mode in terminal use]]></description><category>Uncategorized</category><pubDate>Wed, 03 Jun 2026 15:23:21 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2413</guid><comments>https://bugs.xdebug.org/view.php?id=2413#bugnotes</comments></item><item><title>0002432: eval doesn't support functions like array_map and array_filter</title><author></author><link>https://bugs.xdebug.org/view.php?id=2432</link><description><![CDATA[This was very useful for extracting specific values from arrays of objects, and identifying patterns and counts meeting criteria within an array whilst debugging large data objects.]]></description><category>Step Debugging</category><pubDate>Tue, 02 Jun 2026 20:30:23 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2432</guid><comments>https://bugs.xdebug.org/view.php?id=2432#bugnotes</comments></item><item><title>0002428: XDEBUG_MODE=develop and set_error_handler for deprecated null key in array</title><author></author><link>https://bugs.xdebug.org/view.php?id=2428</link><description><![CDATA[when an error handler is added in the code, the array does not support null keys (which are deprecated as of 8.5.x)]]></description><category>Uncategorized</category><pubDate>Fri, 29 May 2026 15:13:03 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2428</guid><comments>https://bugs.xdebug.org/view.php?id=2428#bugnotes</comments></item><item><title>0002099: Filename path mapping, when using docker/container/vm</title><author></author><link>https://bugs.xdebug.org/view.php?id=2099</link><description><![CDATA[If xdebug provides information about files (e.g. stack traces), we can configure the way it works.&lt;br /&gt;
&lt;br /&gt;
But on my host machine, the files have a different location, then on my guest machine. E.g.: /home/me/project/myapp VS /app&lt;br /&gt;
&lt;br /&gt;
My wish is to have a configuration option, where i could replace a prefix filepath with another prefix.&lt;br /&gt;
&lt;br /&gt;
Something like: &lt;br /&gt;
xdebug.file_map=&quot;/app /home/me/project/myapp&quot;]]></description><category>Uncategorized</category><pubDate>Thu, 28 May 2026 21:49:05 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2099</guid><comments>https://bugs.xdebug.org/view.php?id=2099#bugnotes</comments></item><item><title>0002396: xdebug eval can't define anonymous functions</title><author></author><link>https://bugs.xdebug.org/view.php?id=2396</link><description><![CDATA[it used to be able to do this. It was an invaluable convenience to our whole company for testing our code.]]></description><category>Uncategorized</category><pubDate>Thu, 28 May 2026 14:57:23 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2396</guid><comments>https://bugs.xdebug.org/view.php?id=2396#bugnotes</comments></item><item><title>0002406: Tests failing on armhf with PHP 8.5</title><author></author><link>https://bugs.xdebug.org/view.php?id=2406</link><description><![CDATA[Running the upstream tests in Ubuntu, using PHP 8.5 results in a fail.&lt;br /&gt;
See logs in: &lt;a href=&quot;https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-resolute/resolute/armhf/x/xdebug/20260224_020114_37526@/log.gz&quot; rel=&quot;noopener,nofollow&quot;&gt;https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-resolute/resolute/armhf/x/xdebug/20260224_020114_37526@/log.gz&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
In the logs:&lt;br /&gt;
&lt;br /&gt;
=====================================================================&lt;br /&gt;
520s FAILED TEST SUMMARY&lt;br /&gt;
520s ---------------------------------------------------------------------&lt;br /&gt;
520s Test for bug &lt;a href=&quot;https://bugs.xdebug.org/view.php?id=1343&quot;&gt;0001343&lt;/a&gt;: Wrong values of numerical keys outside 32bit range [tests/develop/bug01343-32bit.phpt]&lt;br /&gt;
520s =====================================================================&lt;br /&gt;
&lt;br /&gt;
Does not say much, but looking at other PHP 8.5 armhf failures, it may be related to a warning about not being able to cast floats outside of the 32 bit range (exactly what the test is about) to int. This warning was not there in PHP8.4, but it's always there in PHP 8.5.]]></description><category>Uncategorized</category><pubDate>Thu, 28 May 2026 14:56:41 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2406</guid><comments>https://bugs.xdebug.org/view.php?id=2406#bugnotes</comments></item><item><title>0002244: xDebug 3.3.x crashes Apache on Ubuntu 22.04 via WSL2; PHP 8.1, seeking resolution.</title><author></author><link>https://bugs.xdebug.org/view.php?id=2244</link><description><![CDATA[Hello xDebug Team,&lt;br /&gt;
&lt;br /&gt;
We've encountered recent issues with version 3.3.x. When enabling the PHP debug extension via the ini file, our PHP crashes (our custom hostname becomes inaccessible, though localhost remains accessible) with Apache, despite the CLI version working fine. Versions equal to or before 3.2.x function without any problems; it's only the latest xDebug version causing issues.&lt;br /&gt;
&lt;br /&gt;
Though we don't have extensive logs, one of our developers encountered segfault errors when enabling the latest xDebug version.&lt;br /&gt;
&lt;br /&gt;
Our development environment consists of:&lt;br /&gt;
&lt;br /&gt;
Platform: Windows Subsystem for Linux (WSL2)&lt;br /&gt;
OS: Ubuntu 22.04&lt;br /&gt;
Web Server: Apache (using supervisor to run apache and mysql services)&lt;br /&gt;
PHP Version: 8.1&lt;br /&gt;
Other enabled PHP extensions on our server include:&lt;br /&gt;
&lt;br /&gt;
ionCube PHP Loader v13.0.2&lt;br /&gt;
Zend OPcache v8.1.27&lt;br /&gt;
We'd appreciate any assistance you can provide in resolving this matter.]]></description><category>Uncategorized</category><pubDate>Wed, 06 May 2026 15:31:24 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2244</guid><comments>https://bugs.xdebug.org/view.php?id=2244#bugnotes</comments></item><item><title>0002420: Introduce separate flags for branch coverage and path coverage collection</title><author></author><link>https://bugs.xdebug.org/view.php?id=2420</link><description><![CDATA[Currently, Xdebug provides a single flag, XDEBUG_CC_BRANCH_CHECK, which activates both branch coverage and path coverage collection simultaneously. I'd like to propose splitting this into two independent flags so that branch coverage and path coverage can be activated separately.&lt;br /&gt;
&lt;br /&gt;
The current design only supports two scenarios:&lt;br /&gt;
&lt;br /&gt;
1. Line coverage only (no flag)&lt;br /&gt;
2. Line coverage + branch coverage + path coverage (XDEBUG_CC_BRANCH_CHECK)&lt;br /&gt;
&lt;br /&gt;
There is no way to enable branch coverage without also enabling path coverage. My assumption is that collecting branch coverage information alone is less resource-intensive than collecting both branch coverage and path coverage. Users who only need branch coverage currently have to pay the additional cost of path coverage collection, even if they do not make use of that data.&lt;br /&gt;
&lt;br /&gt;
Splitting the flag would enable three scenarios:&lt;br /&gt;
&lt;br /&gt;
1. Line coverage only&lt;br /&gt;
2. Line coverage + branch coverage&lt;br /&gt;
3. Line coverage + branch coverage + path coverage&lt;br /&gt;
&lt;br /&gt;
And technically also &quot;line coverage + path coverage&quot;, but I do not see how this would be useful in practice.&lt;br /&gt;
&lt;br /&gt;
I would like to propose two new flags:&lt;br /&gt;
&lt;br /&gt;
- XDEBUG_CC_BRANCH_COVERAGE to activate branch coverage&lt;br /&gt;
- XDEBUG_CC_PATH_COVERAGE to activate path coverage&lt;br /&gt;
&lt;br /&gt;
I am not sure whether or not XDEBUG_CC_PATH_COVERAGE should also activate branch coverage.&lt;br /&gt;
I am aware that the &quot;_CC&quot; infix and the &quot;_COVERAGE&quot; suffix carry redundant information, so the names are not ideal. I have not come up with better names yet, sorry.&lt;br /&gt;
&lt;br /&gt;
In a perfect world, the existing XDEBUG_CC_BRANCH_CHECK flag would be redefined to mean &quot;activate branch coverage only&quot;. However, this would be a backward-compatibility break for existing users who rely on its current behaviour of also activating path coverage. To avoid that, I propose the deprecation of XDEBUG_CC_BRANCH_CHECK and the granular / separate flags shown above.]]></description><category>Code Coverage</category><pubDate>Wed, 29 Apr 2026 09:43:28 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2420</guid><comments>https://bugs.xdebug.org/view.php?id=2420#bugnotes</comments></item><item><title>0002419: Line coverage does not report ternary branch lines when ternary is inside an array literal</title><author></author><link>https://bugs.xdebug.org/view.php?id=2419</link><description><![CDATA[When a multiline ternary operator is used as a value inside an array literal, xdebug_get_code_coverage() does not report coverage data for the lines containing the true and false branch expressions. The same ternary in a simple variable assignment context reports both branch lines correctly.&lt;br /&gt;
&lt;br /&gt;
This affects php-code-coverage (used by PHPUnit). When a ternary operator spans multiple lines inside an array literal, the branch expression lines do not appear in coverage reports at all. They are neither green (executed) nor red (not executed). They are simply not treated as executable lines.&lt;br /&gt;
&lt;br /&gt;
Reported in &lt;a href=&quot;https://github.com/sebastianbergmann/php-code-coverage/issues/1029&quot; rel=&quot;noopener,nofollow&quot;&gt;https://github.com/sebastianbergmann/php-code-coverage/issues/1029&lt;/a&gt;]]></description><category>Code Coverage</category><pubDate>Fri, 24 Apr 2026 09:36:14 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2419</guid><comments>https://bugs.xdebug.org/view.php?id=2419#bugnotes</comments></item><item><title>0002407: Performance issues with 3.5.1 vs 3.4</title><author></author><link>https://bugs.xdebug.org/view.php?id=2407</link><description><![CDATA[I updated my PHP and Xdebug today.&lt;br /&gt;
Some performance testing scripts i have suddenly saw issues.&lt;br /&gt;
Saw the other tickets concerning performance issues and can say 3.5.1 is better compared to 3.5.0 but not to earlier versions.&lt;br /&gt;
&lt;br /&gt;
CPU: AMD 5700G&lt;br /&gt;
All of this was done on PHP 8.3.30 since Xdebug 3.4.7 was not available for PHP 8.5.x.]]></description><category>Uncategorized</category><pubDate>Mon, 23 Mar 2026 19:13:14 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2407</guid><comments>https://bugs.xdebug.org/view.php?id=2407#bugnotes</comments></item><item><title>0002402: Error in xdebug 3.5 with PHP 8.5 when executing code with the pipe operator</title><author></author><link>https://bugs.xdebug.org/view.php?id=2402</link><description><![CDATA[When trying to execute code with the new piper operator, PHP is unable to return the output and reports the error: zend_mn_heap_corrupted (this in the CLI, in the browser it reports error 500)&lt;br /&gt;
&lt;br /&gt;
By disabling xdebug in php.ini, PHP can correctly interpret the code snippets containing the pipe operator.&lt;br /&gt;
Initially I thought it was the Xdebug version, I changed it to the latest version, which is 3.5, and PHP to 8.5.1 and not even with that (I noticed that Xdebug only supports version 8.5.0).&lt;br /&gt;
&lt;br /&gt;
And when writing other codes, PHP with Xdebug enabled runs normally.]]></description><category>Tracing</category><pubDate>Mon, 23 Mar 2026 15:59:06 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2402</guid><comments>https://bugs.xdebug.org/view.php?id=2402#bugnotes</comments></item><item><title>0002394: Can't create control Named Pipe</title><author></author><link>https://bugs.xdebug.org/view.php?id=2394</link><description><![CDATA[I'm always getting:&lt;br /&gt;
&lt;br /&gt;
[25784] Log opened at 2025-12-31 14:45:05.172564&lt;br /&gt;
[25784] [Config] WARN: Can't create control Named Pipe (0x0)&lt;br /&gt;
[25784] Log closed at 2025-12-31 14:45:05.173333&lt;br /&gt;
&lt;br /&gt;
As such, no stop by Xdebug at breakpoint.]]></description><category>Step Debugging</category><pubDate>Mon, 23 Mar 2026 15:36:12 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2394</guid><comments>https://bugs.xdebug.org/view.php?id=2394#bugnotes</comments></item><item><title>0002412: No warning shown before logging out while writing a post.</title><author></author><link>https://bugs.xdebug.org/view.php?id=2412</link><description><![CDATA[If a user is writing a post and accidentally clicks logout, the system logs out immediately without any confirmation. This results in loss of typed content.]]></description><category>Uncategorized</category><pubDate>Sat, 21 Mar 2026 18:36:42 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2412</guid><comments>https://bugs.xdebug.org/view.php?id=2412#bugnotes</comments></item><item><title>0002391: Code Coverage times out on random tests</title><author></author><link>https://bugs.xdebug.org/view.php?id=2391</link><description><![CDATA[We accidentally installed 3.50-dev and then our code coverage started failing. I listed as always reproducible because if we run our entire test suite, it happens every time. However, the particular test that times out varies. &lt;br /&gt;
&lt;br /&gt;
Step 3/3: PHPUnit (Command Line)&lt;br /&gt;
19:24:05   Starting: D:\TeamCityBuildAgent\temp\agentTmp\custom_script1165008140808374324.cmd&lt;br /&gt;
19:24:05   in directory: D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8&lt;br /&gt;
19:26:58   PHPUnit 12.4.1 by Sebastian Bergmann and contributors.&lt;br /&gt;
19:26:58   &lt;br /&gt;
19:26:58   Runtime:       PHP 8.4.14 with Xdebug 3.5.0-dev&lt;br /&gt;
19:26:58   Configuration: D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8\phpunit\phpunit-coverage.xml&lt;br /&gt;
19:26:58   &lt;br /&gt;
19:27:03   D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8\phpunit\phpunit-coverage.xml&lt;br /&gt;
19:29:37   &lt;br /&gt;
19:29:37   Fatal error: Maximum execution time of 120 seconds exceeded in D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8\vendor\phpmailer\phpmailer\src\PHPMailer.php on line 895&lt;br /&gt;
19:29:37   Maximum execution time of 120 seconds exceeded&lt;div style=&quot;background-color:#e8e8e8;height: 20px;&quot;&gt;&nbsp;&lt;/div&gt;&lt;table id=&quot;trace&quot;&gt;&lt;br /&gt;
19:29:37   &lt;tr&gt;&lt;td&gt;#&lt;/td&gt;&lt;td&gt;File:Line&lt;/td&gt;&lt;td&gt;Function&lt;/td&gt;&lt;/td&gt;&lt;br /&gt;
19:29:37   &lt;tr&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;classes\ErrorHandling::errorHandlerShutdown::&lt;/td&gt;&lt;/tr&gt;&lt;br /&gt;
19:29:37   &lt;tr&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;D:\TeamCityBuildAgent\work\9e132eb6cf93e5a8\vendor\phpmailer\phpmailer\src\PHPMailer.php:895&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;br /&gt;
19:29:37   &lt;/table&gt;&lt;div style=&quot;background-color:#e8e8e8;height: 20px;&quot;&gt;&nbsp;&lt;/div&gt;&lt;table id=&quot;arguments&quot;&gt;&lt;br /&gt;
19:29:37   &lt;tr&gt;&lt;td&gt;#&lt;/td&gt;&lt;td&gt;Arguments&lt;/td&gt;&lt;/td&gt;&lt;br /&gt;
19:29:37   &lt;tr&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;br /&gt;
19:29:37   &lt;tr&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;br /&gt;
19:29:37   &lt;/table&gt;Fatal error: Premature end of PHP process when running classes\Controllers\ETL_StatusTest::test_updateETLsToRunNow_AllStaging.&lt;br /&gt;
19:29:37   Process exited with code 255]]></description><category>Code Coverage</category><pubDate>Tue, 24 Feb 2026 14:25:27 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2391</guid><comments>https://bugs.xdebug.org/view.php?id=2391#bugnotes</comments></item><item><title>0002385: Allow IDEKEY/Cloud ID key from php.ini be overridden through XDEBUG_SESSION_START variable if xdebug.start_with_request=yes</title><author></author><link>https://bugs.xdebug.org/view.php?id=2385</link><description><![CDATA[In some cases users might want to have a default Cloud ID key configured in php.ini, with xdebug.start_with_request=yes set. This is useful to intercept and debug requests where the XDEBUG_SESSION_START value is missing. Although this works, this stops Xdebug from using the XDEBUG_SESSION_START altogether if one is present, as xdebug.start_with_request=yes short-circuits the checking for this value.&lt;br /&gt;
&lt;br /&gt;
Subsequently, this means that if XDEBUG_SESSION_START is present, it is not looked at, and the Cloud ID key that it might include is not used.&lt;br /&gt;
&lt;br /&gt;
What instead should happen, is that even with xdebug.start_with_request=yes is set, it should use the XDEBUG_SESSION_START value when connecting to the IDE/Xdebug Cloud, and hence override the hard-coded one from php.ini.]]></description><category>Step Debugging</category><pubDate>Fri, 06 Feb 2026 10:18:35 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2385</guid><comments>https://bugs.xdebug.org/view.php?id=2385#bugnotes</comments></item><item><title>0002222: Xdebug holds a reference to objects in the stack trace of a caught exception</title><author></author><link>https://bugs.xdebug.org/view.php?id=2222</link><description><![CDATA[I think relating to the 3.3.0 release which fixed some issues with exception.&lt;br /&gt;
&lt;br /&gt;
I am now seeing in a Drupal context that objects are not getting their destructor called sometimes when they should. With Xdebug disabled it calls them normally at the end of the method that created them when their variable goes out of scope.&lt;br /&gt;
&lt;br /&gt;
I think it's related to exceptions being rethrown in some cases perhaps it is &quot;capturing&quot; a reference in a stack and then preventing it from destructing.]]></description><category>Tracing</category><pubDate>Tue, 03 Feb 2026 16:31:37 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2222</guid><comments>https://bugs.xdebug.org/view.php?id=2222#bugnotes</comments></item><item><title>0002397: Very slow with Xdebug 3.5.0</title><author></author><link>https://bugs.xdebug.org/view.php?id=2397</link><description><![CDATA[I've installed Xdebug 3.5.0 with PHP versions 8.5, 8.4, 8.3 and all are very slow compared to Xdebug 3.4.x.&lt;br /&gt;
&lt;br /&gt;
Here is test code.&lt;br /&gt;
```&lt;br /&gt;
&lt;?php&lt;br /&gt;
// Start the benchmark&lt;br /&gt;
$start_time = microtime(true);&lt;br /&gt;
&lt;br /&gt;
// Code block to benchmark (example: a simple loop)&lt;br /&gt;
$iterations = 1000000;&lt;br /&gt;
for ($i = 0; $i &lt; $iterations; $i++) {&lt;br /&gt;
    // Perform some operation, e.g., string concatenation&lt;br /&gt;
    $result = &quot;Test string&quot; . $i;&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
// Stop the benchmark&lt;br /&gt;
$end_time = microtime(true);&lt;br /&gt;
&lt;br /&gt;
// Calculate and display the total time taken in seconds&lt;br /&gt;
$total_time = round(($end_time - $start_time), 4);&lt;br /&gt;
echo 'Code execution time: ' . $total_time . ' seconds.';&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
With Xdebug 3.4.x, the result will be around 0.12xxx - 0.13xxx seconds.  &lt;br /&gt;
But with Xdebug 3.5.0 the result go up to 9 seconds+ or more.&lt;br /&gt;
&lt;br /&gt;
Tested with PHP 8.3, 8.4, 8.5 on Windows.&lt;br /&gt;
&lt;br /&gt;
php -v&lt;br /&gt;
&gt; PHP 8.5.0 (cli) (built: Nov 18 2025 08:16:50) (NTS Visual C++ 2022 x64)&lt;br /&gt;
&gt; Copyright (c) The PHP Group&lt;br /&gt;
&gt; Zend Engine v4.5.0, Copyright (c) Zend Technologies&lt;br /&gt;
&gt;     with Xdebug v3.5.0, Copyright (c) 2002-2025, by Derick Rethans&lt;br /&gt;
&gt;     with Zend OPcache v8.5.0, Copyright (c), by Zend Technologies&lt;br /&gt;
&lt;br /&gt;
Web server:  &lt;br /&gt;
Apache/2.4.46 (Win64) OpenSSL/1.1.1i mod_fcgid/2.3.10-dev  &lt;br /&gt;
Non thread safety.  &lt;br /&gt;
Compiler: Visual C++ 2022  &lt;br /&gt;
Architecture: x64&lt;br /&gt;
&lt;br /&gt;
php.ini config:  &lt;br /&gt;
```&lt;br /&gt;
; Xdebug&lt;br /&gt;
zend_extension = 'D:/wwwserver-x64/php/xdebug/php_xdebug-3.5.0-8.5-nts-vs17-x86_64.dll'&lt;br /&gt;
xdebug.profiler_append = 0&lt;br /&gt;
xdebug.start_with_request = trigger&lt;br /&gt;
xdebug.mode = develop,profile&lt;br /&gt;
xdebug.output_dir = 'D:/my-dev-programs/wwwserver-x64/tmp/xdebug'&lt;br /&gt;
xdebug.profiler_output_name = 'cachegrind.out.%p%H%R'&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
Xdebug log:  &lt;br /&gt;
&gt; [8168] Log opened at 2026-01-14 04:42:56.268240&lt;br /&gt;
&gt; [8168] [Config] WARN: Can't create control Named Pipe (0xe7)&lt;br /&gt;
&gt; [8168] [Config] INFO: Trigger value for 'XDEBUG_TRIGGER' not found, falling back to 'XDEBUG_PROFILE'&lt;br /&gt;
&gt; [8168] [Config] INFO: Trigger value for 'XDEBUG_PROFILE' not found, so not activating&lt;br /&gt;
&gt; [8168] Log closed at 2026-01-14 04:43:10.227919]]></description><category>Step Debugging</category><pubDate>Tue, 03 Feb 2026 15:37:31 +0000</pubDate><guid>https://bugs.xdebug.org/view.php?id=2397</guid><comments>https://bugs.xdebug.org/view.php?id=2397#bugnotes</comments></item></channel></rss>
