vscode-php-debug: Version 1.12.0 seems to have broken Debugging
I’ve been debugging in VSCode this morning, but since launch break the Debugger doesn’t work anymore. Doesn’t matter if I try to debug using the local php installation (7.1.1) or a remote one inside a Docker container, starting the debugger throws a “Debug adapter process has terminated unexpectedly”.

There’s no information in any of the output channels or the debug console. The error on the Console does not give any further information either.

my launch.json has not yet been updated to the newest Code workspace settings, but as I said, it worked this morning.
{
"version": "0.2.0",
"configurations": [
{
"name": "Local auf Port 9001",
"type": "php",
"request": "launch",
"port": 9001,
"log": false
},
{
"name": "Launch currently open script",
"type": "php",
"request": "launch",
"program": "${file}",
"cwd": "${fileDirname}",
"port": 9000
},
{
"name": "Listen for XDebug in Docker Webserver Container (OVB)",
"type": "php",
"request": "launch",
"port": 9000,
"serverSourceRoot": "/var/www/wordpress-custom/ovb/wp-content",
"localSourceRoot": "${workspaceFolder}/wp-content",
"log": false
},
{
"name": "Listen for XDebug in Docker Webserver Container (VN,...)",
"type": "php",
"request": "launch",
"port": 9000,
"serverSourceRoot": "/var/www/wordpress-custom/webpapers/wp-content",
"localSourceRoot": "${workspaceRoot}/wordpress-custom/wp-content",
"log": false
},
{
"name": "Listen for XDebug in Importer Docker Container (OVB)",
"type": "php",
"request": "launch",
"port": 9000,
"serverSourceRoot": "/opt/app-root/src/wordpress-custom/ovb/wp-content",
"localSourceRoot": "${workspaceRoot}/wp-content",
"log": false
},
{
"name": "PHPUnit",
"type": "php",
"request": "launch",
"port": 9001,
"program": "/usr/local/bin/phpunit",
"cwd": "${workspaceRoot}",
"args": ["${file}", "-c", "${fileDirname}/../../phpunit.xml"]
}
]
}
Using Code 1.18.1 on macOS 10.12.6 Sierra
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 9
- Comments: 23 (2 by maintainers)
@stereoit posted the following workaround
I apologise for the inconvenience. I automated the release process yesterday night but forgot the build step in the release stage.
Thanks you very much for quick fix
Also just added automatic uploads of vsix files as part of the release process. Seems to have helped a lot of folks today keep working despite the technical difficulties 😃
Thanks Felix! It’s perfect.
Confirmed.
I have disabled “extensions.autoUpdate”, uninstalled 1.12, installed https://github.com/felixfbecker/vscode-php-debug/releases/download/v1.11.1/php-debug-1.11.1.vsix from the Extension Manager and it works again.
Same error. Happened on three machines running Windows 10 Pro, on one of the VS Code installations there were no other extensions except PHP Debug.
Reverting the version to 1.11.1 works as expected.
same error, hours wasted trying fixed it , finally I tried with 1.11.1 and no problems