Unknown circumstances leading to the crash - there is no evidence of what is causing the issue in either the xdebug log file (level set to 10) or the VSCode debug console. I determined it is due to the plugin by a process of elimination. I am using the latest version of the plugin and xdebug (3.5.3). The circumstances as follows:
- The only error I was able to find is in the php-fpm error log which contains
[10-Jun-2026 09:50:35] WARNING: [pool www] child 4863 exited on signal 11 (SIGSEGV) after 8.754265 seconds from start
- the crash occurs when vscode is connected to the debugging session, even if no breakpoints or anything are set.
- the debugger session is being launched by trigger from the browser and completes normally if VSCode is not listening
- the CLI debugger when sending the "run" command after attaching completes successfully
- I attempted to set breakpoints and step through the point of failure, but the line on which it fails appeared to change at random.
- After inspecting the initialisation/handshake output in the xdebug log file I was able to prevent it from crashing by sending
"xdebugSettings": { "breakpoint_include_return_value" : 0 }, in the launch.json file
Please let me know if you want me to dump any output from the environment, I could not find any other output of use while trying to diagnose the issue.
Unknown circumstances leading to the crash - there is no evidence of what is causing the issue in either the xdebug log file (level set to 10) or the VSCode debug console. I determined it is due to the plugin by a process of elimination. I am using the latest version of the plugin and xdebug (3.5.3). The circumstances as follows:
[10-Jun-2026 09:50:35] WARNING: [pool www] child 4863 exited on signal 11 (SIGSEGV) after 8.754265 seconds from start"xdebugSettings": { "breakpoint_include_return_value" : 0 },in the launch.json filePlease let me know if you want me to dump any output from the environment, I could not find any other output of use while trying to diagnose the issue.