warden: warden debug return Segmentation fault error for all different commands
Version of Warden
0.15.0
Operating System and Installation Method
Mac os 15.3, Apple M3 pro
Describe the Bug
When I run a command like bin/magento inside warden shell, it works fine, but when I run it inside warden debug, it returns the below error
Segmentation fault
Do you have any idea what might be the issue?
Magento version: 2.4.7-p2
all commands in warden debug return the error
I am using docker desktop
To Reproduce
- Go to ‘…’
- Click on ‘…’
- Scroll down to ‘…’
- See error
Expected Behavior
No response
Additional context
No response
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 15 (8 by maintainers)
@derickr replied in https://bugs.xdebug.org/view.php?id=2333#c7232 :
https://xdebug.org/docs/compat#compat also states it’s not compatible
I tried disabling ioncube with the following line, and issue is gone.
@bap14 @navarr, maybe we can remove ioncube extension from xdebug images?
Im experiencing the same issue.
Magento version: 2.4.7-p4 Command: bin/magento (any bin/magento command) Warden version: 0.15.0 MacOs: Sequoia 15.1.1 Processor: Apple M4 Im using docker desktop
Im experiencing this with all my project.
That’s not a way to get a possible bug in xdebug fixed.
Hi, I’m having the same issue, and would like to add more notes:
docker.io/wardenenv/php-fpm:8.1-magento2-xdebug3The debugger itself is inside the bin/magento file, and starts execution, then it goes to the symfony cli library, and there it crashes. I believe it’s an xdebug issue.
UPD: I was also able to reproduce this issue on the following code based on symfony/console lib code (require only
symfony/console 6.4.20): https://github.com/symfony/console/blob/2e4af9c952617cc3f9559ff706aee420a8464c36/Command/Command.php#L75-L77Console out:
Next steps: