Skip to content

Temporary console debugging hangs on PowerShell Integrated Console prompt #942

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

Closed
kborowinski opened this issue Jul 7, 2017 · 5 comments · Fixed by PowerShell/PowerShellEditorServices#539

Comments

@kborowinski
Copy link

kborowinski commented Jul 7, 2017

System Details

  • Operating system name and version: Windows 10.0.15063 x64
  • VS Code version: 1.13.1
  • PowerShell extension version: 1.4.1
  • Output from $PSVersionTable:
Name                           Value
----                           -----
PSVersion                      5.1.15063.447
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.15063.447
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

Temporary console debugging hangs on PowerShell Integrated Console prompt.

Note: When "createTemporaryIntegratedConsole" is set to false debugging works as exptected.

Steps to recreate

  • Enable temporary intergrated console debugging in settings
"powershell.debugging.createTemporaryIntegratedConsole": true
  • Set breakpoint in script or module and hit F5
  • Debugging hangs on PowerShell Inegrated Console message

Attached Logs

1499442772-8c16997c-e92b-442f-949d-94aa6756e65b1499442771245.zip

@daviwil
Copy link
Contributor

daviwil commented Jul 11, 2017

Hey Kris, which debugging configuration are you using, is it the one called "PowerShell Interactive Session"?

@daviwil daviwil added this to the July 2017 milestone Jul 11, 2017
daviwil added a commit to daviwil/PowerShellEditorServices that referenced this issue Jul 11, 2017
This change fixes an issue which causes the command prompt to not appear
when you start an interactive debugging session with the
-DebugServiceOnly parameter.  The fix is to invoke the host's command
loop in this specific case.

Resolves PowerShell/vscode-powershell#942
daviwil added a commit to PowerShell/PowerShellEditorServices that referenced this issue Jul 11, 2017
This change fixes an issue which causes the command prompt to not appear
when you start an interactive debugging session with the
-DebugServiceOnly parameter.  The fix is to invoke the host's command
loop in this specific case.

Resolves PowerShell/vscode-powershell#942
@kborowinski
Copy link
Author

kborowinski commented Jul 11, 2017 via email

@daviwil
Copy link
Contributor

daviwil commented Jul 11, 2017

Cool! Just fixed it, it'll be in the next update.

@kborowinski
Copy link
Author

Do I miss something? It still does not work in PowerShell 1.4.2 extension.

@daviwil
Copy link
Contributor

daviwil commented Oct 27, 2017

Hey @kborowinski, sorry for the delay on this, it's going out with the update I'm shipping today!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants