0002333: Segmentation fault while using symfony console with xdebug

ID	Project	Category	View Status	Date Submitted	Last Update
0002333	Xdebug	Uncategorized	public	2025-04-08 09:19	2025-04-11 10:18

Reporter	isviziev	Assigned To
Priority	normal	Severity	major	Reproducibility	always
Status	resolved	Resolution	no change required
Product Version	3.4.2

Summary	0002333: Segmentation fault while using symfony console with xdebug
Description	Hi, I noticed that the Magento 2 command line fails with a Segmentation fault when xdebug is enabled (originally reported in https://github.com/wardenenv/warden/issues/843). Once xdebug is disabled, the issue will not be reproduced. The interesting part is that debug actually works at the beginning, but then fails when the symfony console component initializes and executes the following code https://github.com/symfony/console/blob/6.4/Command/Command.php#L71-L77 I was able to restrict it to the Symfony console component so we can easily reproduce it.
Steps To Reproduce	composer require symfony/console:^6.4 Run the attached PHP file as php test.php
Additional Information	$ php -v PHP 8.1.32 (cli) (built: Mar 11 2025 22:09:20) (NTS gcc aarch64) Copyright (c) The PHP Group Zend Engine v4.1.32, Copyright (c) Zend Technologies with the ionCube PHP Loader v14.4.0, Copyright (c) 2002-2025, by ionCube Ltd. with Zend OPcache v8.1.32, Copyright (c), by Zend Technologies with Xdebug v3.4.2, Copyright (c) 2002-2025, by Derick Rethans
Tags	No tags attached.

Operating System	macOS 15.4 (arm), Ubuntu Linux 24.04 (amd64)
PHP Version	8.1.30-8.1.39

isviziev 2025-04-08 10:25 reporter ~0007230	Note: when running xdebug in disabled mode - script executes successfully. XDEBUG_MODE=off php test.php

derick 2025-04-08 12:47 administrator ~0007232	Xdebug isn't compatible with "ionCube". Can you turn that one off to see whether you can still reproduce it? I can't locally. And your attached `xdebug.log` also sees a normal debug connection, although your IDE decides to `detach` without running code (that's an IDE issue).

isviziev 2025-04-08 13:43 reporter ~0007243	Hi Derick, Thank you so much for your reply! I've turned off the ionCube, and the issue is gone. Thank you so much for a prompt reply!

isviziev 2025-04-08 13:44 reporter ~0007244	Just wonder... why ioncube adds something to the code that isn't generated by ioncube... Never mind, it's a question for ionCube, not for xdebug

derick 2025-04-11 10:18 administrator ~0007245	ionCube changes the executor in PHP. As it's closed source I have no idea what they're doing with it, nor can I check it out. Glad that the Xdebug crash now went away!