Please follow the instructions at https://xdebug.org/reporting-bugs while reporting bug reports.

This is however possibly a duplicate of https://bugs.xdebug.org/view.php?id=2307, which has reportedly been fixed with https://github.com/xdebug/xdebug/pull/987, and is part of the xdebug_3_4 branch on Github.

cheers,
Derick

Thanks for your reply,
What information can I provide in addition to attached reproducing environment?

I am not sure if this is exact duplicate of https://bugs.xdebug.org/view.php?id=2307
On my reproducer and my php + xdebug configs the code form that issue is not failing with segfault.
It do fails when I change mode and run as XDEBUG_MODE=develop,trace php test.php

To check if mentioned fix help should we to try to compile xdebug from latest xdebug_3_4 or wait for release of 3.4.1 ?

Xdebug 3.4.1 will be released imminently (an hour), so wait for that.

On our side we still have the issue even after upgrading Xdebug to last release

PHP 8.3.15 (cli) (built: Dec 24 2024 22:23:49) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.15, Copyright (c) Zend Technologies
with Zend OPcache v8.3.15, Copyright (c), by Zend Technologies
with the ionCube PHP Loader v14.0.0, Copyright (c) 2002-2024, by ionCube Ltd.
with Xdebug v3.4.1, Copyright (c) 2002-2025, by Derick Rethans

@NicolasD — Xdebug does not support being loaded with ionCube at the same time. Can you disable that? And if you can still reproduce it, please create a new issue as it is likely different than this one.

I did some extended testing with my reproducer and xdebug 3.4.1

The issue still present
But it only fails for develop mode

Works OK:
XDEBUG_MODE=debug ./vendor/bin/magento-patches -n status

Works NOT OK:
XDEBUG_MODE=develop ./vendor/bin/magento-patches -n status

I use this env
XDEBUG_MODE=develop,debug

Current setup:

PHP 8.1.23 (cli) (built: Sep 20 2023 19:22:02) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.23, Copyright (c) Zend Technologies
with Zend OPcache v8.1.23, Copyright (c), by Zend Technologies
with Xdebug v3.4.1, Copyright (c) 2002-2025, by Derick Rethans
with blackfire v1.92.31~linux-x64-non_zts81, https://blackfire.io, by Blackfire

I wondered if XDEBUG_MODE=develop might conflict with other profilers like blackfire and spx due to function overloading or neighbors decorators overlapping. But it previously worked just fine to me.

I also followed some steps with GDB and got this result:

Starting program: /usr/local/bin/php ./vendor/bin/magento-patches -n status
warning: Error disabling address space randomization: Operation not permitted
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Patch details you can find on https://experienceleague.adobe.com/tools/commerce-quality-patches/index.html (search for patch id, ex. MDVA-30265)
Release notes https://experienceleague.adobe.com/docs/commerce-operations/tools/quality-patches-tool/release-notes.html
[Detaching after fork from child process 418]
[Detaching after fork from child process 419]

Program received signal SIGSEGV, Segmentation fault.
0x00007f01b125b929 in zval_from_stack_add_frame_variables (opa=0x7f01af72fc00, symbols=<optimized out>, edata=0x7f01b1415dc0,
frame=0x7f01b14621d0) at /tmp/pear/temp/xdebug/src/develop/stack.c:431
431 /tmp/pear/temp/xdebug/src/develop/stack.c: No such file or directory.

full output in gdb.txt

Do you still get this error without blackfire too?
I had/have a similar issue and while checking various similar issues, one common thing was that blackfire was being used