VS Code Powershell debugger hanging - PS 7 with Powershell extension

[bkarlow-optimo]

Issue Description

I am experiencing a problem with... VSCode debugger with Powershell integrated console set to Powershell Core version 7.1.3. The debugger launches, finds the first breakpoint in the entry point PS1 script file, executes to the first breakpoint - all good.

Immediately upon stepping over the breakpoint (F10), debugger hangs, terminal is non-responsive.

This MAY be related to #3410 , but unclear.

This is reproduceable.

VS Code settings:

{
"powershell.powerShellAdditionalExePaths": [
{
"exePath": "C:\Program Files\PowerShell\7\pwsh.exe",
"versionName": "PowerShell 7"
}
],
"powershell.powerShellDefaultVersion": "PowerShell 7",
"terminal.integrated.automationShell.windows": "C:\Program Files\PowerShell\7\pwsh.exe",
"terminal.external.windowsExec": "C:\Program Files\PowerShell\7\pwsh.exe",
"terminal.integrated.automationShell.osx": "",
"terminal.integrated.automationShell.linux": "",
"debug.javascript.autoAttachFilter": "smart",
"vs-kubernetes": {
"vscode-kubernetes.kubectl-path.windows": "C:\Users\genericuser\.vs-kubernetes\tools\kubectl\kubectl.exe",
"vscode-kubernetes.minikube-path.windows": "C:\Users\genericuser\.vs-kubernetes\tools\minikube\windows-amd64\minikube.exe",
"vscode-kubernetes.helm-path.windows": "C:\Users\genericuser\.vs-kubernetes\tools\helm\windows-amd64\helm.exe"
},
"mssql.connections": [
{
"server": "{{put-server-name-here}}",
"database": "{{put-database-name-here}}",
"user": "{{put-username-here}}",
"password": "{{put-password-here}}"
}
],
"editor.codeActionsOnSave": {
"source.fixAll.eslint": true
},
"terminal.integrated.profiles.windows": {
"PowerShell": {
"source": "PowerShell",
"icon": "terminal-powershell",
"path": "C:\Program Files\PowerShell\7\pwsh.exe"
},
"Command Prompt": {
"path": [
"${env:windir}\Sysnative\cmd.exe",
"${env:windir}\System32\cmd.exe"
],
"args": [],
"icon": "terminal-cmd"
},
"Git Bash": {
"source": "Git Bash"
},
"PowerShell 7": {
"path": "C:\Program Files\PowerShell\7\pwsh.exe",
"args": []
}
}
}

Attached Logs

EditorServices.log
StartEditorServices.log
vscode-powershell.log

Environment Information

Visual Studio Code

Name	Version
Operating System	Windows_NT x64 10.0.19043
VSCode	1.57.0
PowerShell Extension Version	2021.5.1

PowerShell Information

Name	Value
PSVersion	7.1.3
PSEdition	Core
GitCommitId	7.1.3
OS	Microsoft Windows 10.0.19043
Platform	Win32NT
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.10032.0 6.0.0 6.1.0 6.2.0 7.0.0 7.1.3
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1
WSManStackVersion	3.0

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

Extension	Author	Version
armview	bencoleman	0.4.5
azure-account	ms-vscode	0.9.8
azure-pipelines	ms-azure-devops	1.188.1
azurecli	ms-vscode	0.5.0
azurerm-vscode-tools	msazurermtools	0.15.1
debugger-for-chrome	msjsdiag	4.12.12
markdown-all-in-one	yzhang	3.4.0
mssql	ms-mssql	1.10.1
npm-intellisense	christian-kohler	1.3.1
powershell	ms-vscode	2021.5.1
remote-containers	ms-vscode-remote	0.183.0
remote-wsl	ms-vscode-remote	0.56.5
rest-client	humao	0.24.5
vscode-aks-tools	ms-kubernetes-tools	0.0.8
vscode-apimanagement	ms-azuretools	1.0.2
vscode-azureappservice	ms-azuretools	0.22.0
vscode-azurefunctions	ms-azuretools	1.4.0
vscode-azureresourcegroups	ms-azuretools	0.4.0
vscode-azurestorage	ms-azuretools	0.12.1
vscode-azurevirtualmachines	ms-azuretools	0.4.0
vscode-bicep	ms-azuretools	0.4.63
vscode-commons	redhat	0.0.6
vscode-cosmosdb	ms-azuretools	0.16.0
vscode-docker	ms-azuretools	1.13.0
vscode-dotnet-runtime	ms-dotnettools	1.1.0
vscode-eslint	dbaeumer	2.1.23
vscode-kubernetes-tools	ms-kubernetes-tools	1.3.3
vscode-markdownlint	DavidAnson	0.42.1
vscode-node-azure-pack	ms-vscode	0.2.1
vscode-npm-script	eg2	0.3.22
vscode-yaml	redhat	0.19.2

[strickdd]

I'm having a very similar issue, but the debugger never hits the first breakpoint and I'm using PS 5.1. It shows the toolbar (screenshot below), but never hits the breakpoint and the terminal hangs - can't scroll or type.

Debug Toolbar

Simple Script

function Get-SomeVal {
    # Breakpoint on this line
    'Some Val' | Write-Output
}

Get-SomeVal

Logs
EditorServices.log
PowerShellEditorServices.log
StartEditorServices.log
vscode-powershell.log

Code Version

PS:\>code -v
1.57.1
507ce72a4466fbb27b715c3722558bb15afa9f48
x64

Extensions

PS:\>code --list-extensions --show-versions
eamodio.gitlens@11.5.1
mhutchie.git-graph@1.30.0
ms-azuretools.vscode-docker@1.14.0
ms-dotnettools.csharp@1.23.12
ms-vscode-remote.remote-containers@0.183.0
ms-vscode-remote.remote-wsl@0.56.5
ms-vscode.powershell@2021.6.1
ms-vscode.vs-keybindings@0.2.1
shd101wyy.markdown-preview-enhanced@0.5.21
slevesque.vscode-autohotkey@0.2.2

Editor Services Version

PS:\>$psEditor.EditorServicesVersion


Major  Minor  Build  Revision
-----  -----  -----  --------
2      4      4      0       

PSVersion Table

PS:\>$PSVersionTable


Name                           Value
----                           -----
PSVersion                      5.1.18362.1474
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.1474
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

UPDATE
On a whim, I switched to PS 7.1 and it now hits the breakpoint, but once I step over it, I am taken to a "weird" file location in debug mode (screenshot below). Once I hit "F5" to continue, the terminal just hangs and the debug tollbar stays. Clicking the "Stop" on the debug toolback does nothing. I have to kill the terminal session and let it restart to proceed.

"Weird" file after F10:

Hanging debugger:

[strickdd]

Not sure if it matters, but highlighting code and pressing F8 runs that section of code without issue.

[andyleejordan]

Hey, just an FYI we are actively working on PowerShell/PowerShellEditorServices#1295 which re-wires the debugger. Hence we are prioritizing that rather than fixing issues with the existing implementation. We intend to have that in the next preview, and then we will see if this problem goes away 😄

[bkarlow-optimo]

@strickdd -
Thanks for the feedback. I'm glad I'm not the only one experiencing similar issues.

@andschwa -
Thank you for the feedback. Understood regarding focus on new implementation of the debugger, and that is great news. I still think it important to raise these issues so others are aware they are not alone.

Any target release date for the new debugger? I read through the referenced thread and saw a mentioned target date of EOY 2020, which obviously is no longer accurate.

[andyleejordan]

The whole year of 2020 was...a mess, for everyone (also I was not yet a maintainer here). We are planning to get it into the next release, hopefully end of this month, potentially next month, but not much later than that!

[bkarlow-optimo]

@andschwa - Thank you for the update. I suppose I can work around this issue for now. Regards.

[peetrike]

The problem might be connected to PSReadline v2.2.0-Beta3 (reported in PowerShell/PSReadLine#2616)

[andyleejordan]

If that is the case, could @peetrike and @bkarlow-optimo try ensuring you only have PSReadLine 2.1.0 on the machine?

#3393 (comment)

I will try to prioritize this: PowerShell/PowerShellEditorServices#1493

[strickdd]

I know I wasn't in the list, but in case it helps... here are my available PSReadline modules.