-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug adapter has terminated unexpectedly #1542
Comments
Also getting the same debug termination error when debugging any script in extension version 1.8.4, logs do not show anything obvious but crash always generates a "Socket closed, shutting down." message in DebugAdapter.log which is probably to be expected, but not seeing anything else even with Verbose logging enabled. |
Still an issue in v1.90, it looks like it's an EditorServices issues as I managed to pull the following from it's log (Running on Windows 7 with Powershell V3) :- 2018-10-03 14:18:07.753 [ERROR] C:\PowerShellEditorServices\src\PowerShellEditorServices.Protocol\MessageProtocol\ProtocolEndpoint.cs: In method 'OnListenTaskCompleted', line 391:
2018-10-03 14:18:07.753 [ERROR] C:\PowerShellEditorServices\src\PowerShellEditorServices.Host\EditorServicesHost.cs: In method 'ProtocolEndpoint_UnhandledException', line 435: |
I'm going to dupe this to #1494 so we can keep all the discussion there. |
System Details
Windows 10 version 1803 build 17134.285
1.27.2 (user setup)
v1.8.4
$PSVersionTable
:Issue Description
When I attempt to run the debugger on a powershell script, I get an error saying
If I hit F8, I get the error:
Attached Logs
Followed the instructions for collecting logs in the README, but there are no log files being generated. Log directory does not exist under $HOME.vscode\extensions\ms-vscode.powershell-1.8.4
EDIT
Created logs directory, and DebugAdapter.log was generated successfully.
DebugAdapter.log
Additionally, running the command
returns the error
Troubleshooting steps taken
Not really sure what else to do. Any guidance would be appreciated.
The text was updated successfully, but these errors were encountered: