Breakpoint not being hit when attaching to debugger

System Details

Windows10

System Details Output

Issue Description

I am experiencing a problem as the breakpoints are not getting hit when attaching debugger to different pwsh window.

Expected Behaviour

–It should stop at breakpoint

Actual Behaviour

– It just executed without halting

Attached Logs

vscode-powershell.log StartEditorServices.log EditorServices.log

[Noctran]

I experience the same problem and can agree with the above descriptions.

[IAmIlliest]

Yep, confirming the same symptoms as Leo above. Probably unrelated, but just in case it isn’t, I’m using Conda environments.

For what it’s worth, I’m doing the bits below in a condition where VS Code PS Extension is no longer able to attach to another host process (it times out). Using PS 7.1.3:

• I can attach to the other (first) PS Host process from a second (external to VS Code) PS instance.
• I can also still attach to the other (first) PS Host from the internal terminal in VS Code.
• Once attached, I can set breakpoints in the other (first) PS Host process for the script and see that Get-PSBreakpoints is showing them.
• I can then seemingly successfully enter to begin to debug the runspace that the script will be executing in on the other (first) PS Host process.
• I then run the script, initiating it ‘locally’ on the other (first) PS Host process.
• In both cases, those breakpoints will be ignored.

As such, it seems like the issue is not just VS Code or the PS extension in VS Code, Something is happening that is making the debugging engine for PS ‘non-responsive’ to breakpoints, or else it isn’t attaching properly (despite appearing to report that it is).

Or, I’m missing something else…