Skip to content

Break Points do not clear for Powershell #1037

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
weinand opened this issue Sep 28, 2017 · 4 comments
Closed

Break Points do not clear for Powershell #1037

weinand opened this issue Sep 28, 2017 · 4 comments

Comments

@weinand
Copy link

weinand commented Sep 28, 2017

From @Steve-Lewis on August 22, 2017 16:1

  • VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T18:05:38.342Z)
  • OS Version: Windows_NT ia32 10.0.15063
  • Extensions:
Extension Author (truncated) Version
vscode-eslint dba 1.2.11
xml Dot 1.9.2
vscode-html-css ecm 0.1.8
rest-client hum 0.15.2
csharp ms- 1.12.1
PowerShell ms- 1.4.1
team ms- 1.122.0
html-css-class-completion Zig 1.8.1

Steps to Reproduce:

  1. Open a powershell file
  2. Set a breakpoint by clicking left of the number
  3. Hit F5
  4. Run your powershell
  5. You should break on the breakpoint set in step 2
  6. Step over until the code completed
  7. Clear the breakpoint you set in step 2 the same way you set it
  8. Run your powershell
  9. Breakpoint hits again

Note:
If you type - Get-PSBreakPoint it will output the breakpoints you set in step 2 and tried to clear in Step 7.
Type Get-PSBreakPoint | Remove-PsBreakPoint to remove the break points and you should be able to run the code again without it stopping.

Reproduces without extensions: Yes/No

Copied from original issue: microsoft/vscode#32968

@mattmcnabb
Copy link
Contributor

@weinand this is a duplicate of #625 and is due to VSCode's debugger implementation.

@daviwil
Copy link
Contributor

daviwil commented Sep 28, 2017

@mattmcnabb the irony here is that @weinand is the author of VS Code's debugger ;) #625 is actually something that needs to be fixed on my side.

@daviwil
Copy link
Contributor

daviwil commented Sep 28, 2017

There was one part of the issue that VS Code's debugger played a role in but they just fixed that a couple of days ago. Hopefully I'll get to finish the work on this soon.

Resolving as duplicate of #625.

@daviwil daviwil closed this as completed Sep 28, 2017
@mattmcnabb
Copy link
Contributor

@weinand @daviwil well that's embarrassing!

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

No branches or pull requests

3 participants