Skip to content

Unable to step into class in debug time or hit breakpoint in class #1752

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
rudolfvesely opened this issue Feb 8, 2019 · 5 comments
Closed
Labels
Area-Debugging Bug: VS Code Bugs in VS Code itself.

Comments

@rudolfvesely
Copy link

rudolfvesely commented Feb 8, 2019

Hi all,

I hope this will be helpful. Please let me know if you have any questions.

  • Operating system name and version: Linux, KDE Plasma 5
  • VS Code version: 1.31
  • PowerShell extension version: 1.11.0
### VSCode version: 1.31.0 x64

### VSCode extensions:
[email protected]
[email protected]
[email protected]


### PSES version: 

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      6.1.2
PSEdition                      Core
GitCommitId                    6.1.2
OS                             Linux 4.19
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Issue Description

I'm unable to step into class in debug time or hit breakpoint in class. This wasn't problem in previous versions.

How to test

Create function and class
Instantiate object in function
Try to step into line where you instantiate object, for example [ClassName]::new('foor', 'bar')

Expected Behaviour

Step into

Actual Behaviour

Nothing

@rudolfvesely
Copy link
Author

I've just tested that the bug is not present in VSCode 1.30.2. In other words version 1.31.0 broke something in the PowerShell extension 1.11 and 2.0 Preview.

workaround: downgrade VSCode

@AndyP2
Copy link

AndyP2 commented Feb 9, 2019

I wonder if this is related to issue #1750, which also suggests a change made in vscode 1.31 has broken stepping through code in the powershell debugger.

@rudolfvesely
Copy link
Author

Good point Andy, the class that I mentioned is "used" using using module so it's in different directory.

@SydneyhSmith
Copy link
Collaborator

Thanks for reporting this @rudolfvesely it would also be really helpful if you could attach any logs you have when this occurs, instructions for how to do this are here

@SydneyhSmith
Copy link
Collaborator

Going to close this as a duplicate of #1750 please follow that issue for any developments, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Debugging Bug: VS Code Bugs in VS Code itself.
Projects
None yet
Development

No branches or pull requests

3 participants