Skip to content
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

Debugging untitled file non-workspace window hangs due to cwd being set incorrectly #655

Closed
daviwil opened this issue Apr 6, 2017 · 0 comments
Labels
Milestone

Comments

@daviwil
Copy link
Contributor

daviwil commented Apr 6, 2017

Steps:

  1. Open VS Code without a workspace path (don't load a folder)
  2. Create a new file with Ctrl+N and set its language mode to PowerShell
  3. Write Get-Process in the file
  4. Press F5
  5. Debugger hangs, logs complain about setting cwd with path of untitled:Untitled-1
@daviwil daviwil added Area-Debugging Issue-Bug A bug to squash. labels Apr 6, 2017
@daviwil daviwil added this to the 0.12.2 milestone Apr 6, 2017
daviwil added a commit to daviwil/vscode-powershell that referenced this issue Apr 6, 2017
This change fixes an issue with untitled file paths being sent in the
cwd parameter to debug adapter when in a window that doesn't have a
workspace loaded.  The fix is to change our cwd selection logic to be
more aware of an untitled file being used.

Resolves PowerShell#655.
daviwil added a commit to daviwil/vscode-powershell that referenced this issue Apr 6, 2017
This change fixes an issue with untitled file paths being sent in the
cwd parameter to debug adapter when in a window that doesn't have a
workspace loaded.  The fix is to change our cwd selection logic to be
more aware of an untitled file being used.

Resolves PowerShell#655.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant