_From @Yagneshdxt on March 12, 2017 11:26_
|Extension|Author|Version|
|---|---|---|
|php-debug|felixfbecker|1.10.0|
|php-intellisense|felixfbecker|1.1.3|
|csharp|ms-vscode|1.7.0|
|mono-debug|ms-vscode|0.15.3|
|laravel-blade|onecentlin|1.8.1|;
Steps to Reproduce:
My debugging was working fine before vscode update after vscode update it started showing this error.
_Copied from original issue: Microsoft/vscode#22476_
@Yagneshdxt Is this happening consistently? Can you share the error you see in the debug console and developer console if any?
cc @felixfbecker
_From @felixfbecker on March 12, 2017 18:32_
Feel free to move the issue, I need to see some stack trace from eg dev tools
I'm having the same issue with vs code 1.10.2 on osx.

Hi @ramya-rao-a please find attached screen shot
If you can help me with steps to get more details about error.
I will happy to help you with more detail error log.
What is your launch.json?
EACCESS 81 indicates you use port 81 but don't run with root permissions to bind on that port.
{
"version": "0.2.0",
"configurations": [
{
"name": "Listen for XDebug",
"type": "php",
"request": "launch",
"port": 9000
},
{
"name": "Launch currently open script",
"type": "php",
"request": "launch",
"program": "${file}",
"cwd": "${fileDirname}",
"port": 81
}
]
}
This is my launch.json Please let me know what else can I do
The port setting needs to match what you set in your php.ini config as xdebug.remote_port (default 9000). You cannot listen on ports below 1000 without administrator privileges. Please refer to the readme and xdebug documentation for further help.
@felixfbecker
My debugger was working fine before I updated VSCode. I never faced any issue. I have not changed any access or any of the setting but suddenly after update it stopped working.
Please help me further. I am not able to find any access issue. I ran VSCode with administrator right but I got the same error.
Please find below my port setting in php.ini file.
; Local Variables:
; tab-width: 4
zend_extension = "D:\Yagnesh\php\ext\php_xdebug-2.5.1-7.1-vc14-nts.dll"
xdebug.remote_enable = 1
xdebug.remote_autostart = 1
xdebug.remote_port = 9000
; End:
Well maybe VS Code broke running as admin. But the log in your screenshot clearly shows listen EACCESS 0.0.0.0:80. Which corresponds to your port setting in launch.json - change the port to 9000
I had a different case lately that was not related to port number... Not sure if this is the cause of the problem but this extension doesn't work reliably when there are many concurrent requests being processed. When there are 4-5+ items in call stack and I hit the restart icon (green round arrow) it always crashes with the above message.
I managed to reproduce this consistently with a sample project attached to this comment. In this project index.php file is sending multiple ajax requests at the same time. In file2.php - file7.php there is sleep(30) to keep the process in call stack for a while. Try opening file8.php and create new breakpoint somewhere in the top. Than reload the browser where index.php is opened and once the breakpoint is hit try to restart the debug process (that green arrow or ctrl + shift + f5).

https://drive.google.com/file/d/0B7Ls870jI1CLZWFkazdySHdBTFE/view?usp=sharing
@levani that is a different issue, please don't hijack the thread. XDebug's protocol is serial, so if your script is in a running state (not stopped on a breakpoint or ended) because of a sleep or whatever, we cannot send it the request to terminate, so we have to wait until it returns a stopped response. If you impatiently spam the restart button, then VS Code will just spawn a new debug adapter despite the old one not properly terminated which results in an EADDRINUSE error because the port is still blocked by the other process. This is a different error than EACCESS.
same for me, after update i can not debug with xDebugger
Version : 1.18.1
So : Win 10
Got this problem too like @bakeiro and I used php_xdebug-2.5.5-5.6-vc11
@felixfbecker
After the recent VSCode update I get the above error each time I attempt to debug. This worked fine before the update. This is my launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "Listen for XDebug",
"type": "php",
"request": "launch",
"port": 9000,
"pathMappings": {
"/mnt/[path to my remote working directory]": "${workspaceRoot}/site"
}
}
]
}
@bakeiro same is happening with on my system after update.
Same issue here. Left work yesterday with it working fine and came in today to it being broken. I haven't changed anything.
VSCode 1.18.1
MacOS High Sierra 10.13.1
I started having the same issue a few hours ago.
VSCode 1.18.1
Windows 10
Same issue started for me : Debug adapter process has terminated unexpectedly
VSCode 1.18.1
Windows 10
Same problem VSCode 1.18.1
Ubuntu linux 17.10
[14660:1121/123011.834411:INFO:CONSOLE(5)] "[uncaught exception]: Error: read ECONNRESET", source: file:///usr/share/code/resources/app/out/vs/workbench/electron-browser/bootstrap/index.js (5)
[14660:1121/123011.834460:INFO:CONSOLE(5)] "Error: read ECONNRESET
at exports._errnoException (util.js:1050:11)
at Pipe.onread (net.js:581:26)", source: file:///usr/share/code/resources/app/out/vs/workbench/electron-browser/bootstrap/index.js (5)
[14660:1121/123011.834476:INFO:CONSOLE(163)] "Uncaught Error: read ECONNRESET", source: events.js (163)
[14660:1121/123011.835207:INFO:CONSOLE(9)] "Debug adapter process has terminated unexpectedly", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.main.js (9)
[14660:1121/123012.921884:INFO:CONSOLE(5)] "[uncaught exception]: Error: read ECONNRESET", source: file:///usr/share/code/resources/app/out/vs/workbench/electron-browser/bootstrap/index.js (5)
[14660:1121/123012.921920:INFO:CONSOLE(5)] "Error: read ECONNRESET
at exports._errnoException (util.js:1050:11)
at Pipe.onread (net.js:581:26)", source: file:///usr/share/code/resources/app/out/vs/workbench/electron-browser/bootstrap/index.js (5)
[14660:1121/123012.921937:INFO:CONSOLE(163)] "Uncaught Error: read ECONNRESET", source: events.js (163)
[14660:1121/123012.922326:INFO:CONSOLE(9)] "Debug adapter process has terminated unexpectedly", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.main.js (9)
I had same problem after updating to VSCode 1.18.1 on Windows 10.
I tried a reboot and restarted VSCode. When it opened up, it opened the User Settings file. I have a custom block for the php version 5.4 that I use. This had some errors marked. I'm not sure if these errors were a result of the VSCode update or not. Anyway, I fixed the errors and restarted VSCode.
Still not working.
Then I noticed in my list of Extensions, the PHP Debug extension had an update button. I don't know what version it was, but after clicking on it, it's now at 1.12.1 and it's back working again.
Confirm the bug!!!
Ubuntu 16.04 LTS
Version 1.17.2
and insider version (1.19)
I have the same problem after update.
Also DEB packages were not updated properly (installation script hanged up)
This problem is serious.. do something with it already, please
I am also facing the same issue whenever I tries to step into the debugger stops with error :
debug adapter process has terminated unexpectedly
Here is my launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "Listen for XDebug",
"type": "php",
"request": "launch",
"port": 9000
},
{
"name": "Launch currently open script",
"type": "php",
"request": "launch",
"program": "${file}",
"cwd": "${fileDirname}",
"port": 9000
}
]
}
Can confirm the error.
Windows 8
PHP 7.1.8

Below my launch.json file
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Listen for XDebug",
"type": "php",
"request": "launch",
"port": 9000
},
{
"name": "Launch currently open script",
"type": "php",
"request": "launch",
"program": "${file}",
"cwd": "${fileDirname}",
"port": 9000
}
]
}
Any fix for this error?
Hi All,
I had same issue while I was start using VSCode. Well i took 3 hours to figure out what is exactly issue, I just stared with some step by step debugging like what port being used and what are the other settings.
Finally I was lucky and got the solutions :) So I created a page to share with everyone. You can check what is my findings and what you should need to setup to get Xdebug work with VSCode.
Link: How-to-setup-PHP-Debugging-xdebug-with-VSCode-Visual-Studio-Code
Hope my experience would be helpful for someone. Cheers!!!
Had the same issue this morning, worked yesterday night, updated VSCode to 1.22 and got the error above. Changed php.ini and launch.json to use port 9002, confirmed via netstat that nothing was using either 9000 or 9002, went back to VSCode 1.21, nothing. Had to disable auto-update and go back to PHP Debug 1.11 and now it works.
Same here. Updated VSCode to 1.22.2 and got the error.
@loppp @arby50 could you file a new issue, including some log output? You can always rollback to previous versions in the meantime: https://github.com/felixfbecker/vscode-php-debug/issues/149#issuecomment-381026098
Most helpful comment
Confirm the bug!!!
Ubuntu 16.04 LTS
Version 1.17.2
and insider version (1.19)
I have the same problem after update.
Also DEB packages were not updated properly (installation script hanged up)
This problem is serious.. do something with it already, please