You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a breakpoint is removed while the debugger is active (not at a breakpoint), the debugger functionality breaks. I believe it is still hitting breakpoints but not displaying that they have been hit, and it hangs when attempting to debug again.
To reproduce:
Open VSCode and save the script below.
$start = Get-Date
while ((New-Timespan -Start $start -end (get-date)).Seconds -lt 15) {
Write-Host "Blah!" # <-- Set a breakpoint here
Start-Sleep -Seconds 5
}
Set a breakpoint as indicated and start debugging the script.
When the breakpoint is hit, press F5 (continue) and remove the breakpoint before it is hit again.
After about 5 seconds, I noticed that the pause icon changed to a play icon and the "Hit Line breakpoint" message appeared in the terminal, but no breakpoint indication was present in the editor. Neither F5 or clicking the continue button resumed the script. Clicking the stop button a few times stopped the debugging. Attempting to re-run caused the debug controls to display, but debugging did not start and the execute command which usually appears in the terminal did not display.
Restarting the PowerShell session returned the debugger to normal.
System Details
Issue Description
When a breakpoint is removed while the debugger is active (not at a breakpoint), the debugger functionality breaks. I believe it is still hitting breakpoints but not displaying that they have been hit, and it hangs when attempting to debug again.
To reproduce:
After about 5 seconds, I noticed that the pause icon changed to a play icon and the "Hit Line breakpoint" message appeared in the terminal, but no breakpoint indication was present in the editor. Neither F5 or clicking the continue button resumed the script. Clicking the stop button a few times stopped the debugging. Attempting to re-run caused the debug controls to display, but debugging did not start and the execute command which usually appears in the terminal did not display.
Restarting the PowerShell session returned the debugger to normal.
Attached Logs
logs.zip
The text was updated successfully, but these errors were encountered: