Attach to host process freezes PS Console and do not break in VSCode

[carlos-ricciardi]

Until version 1.8.4 it works: you are able to attach to a PS Console process, start a script and debug in VScode. Starting with 1.9.0 this has stopped working. When you attach VScode to a PS console process it freezes the process, the code doesn't break in VSCode and a message is displayed: To end the debugging session type the ‘Detach’ command at the debugger prompt, or type ‘Ctrl+C’ otherwise.

[TylerLeonhardt]

Thanks for the info! Can you also attach the logs here so we can get a better idea of what's going on?

Also, please upgrade to the latest version of the PowerShell extension - 1.10.2 (at this time)

[carlos-ricciardi]

logs.zip

VSCode version:

Version: Code 1.30.1 (dea8705087adb1b5e5ae1d9123278e178656186a, 2018-12-18T18:12:07.165Z)
OS Version: Windows_NT x64 10.0.17134
CPUs: Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz (8 x 3492)
Memory (System): 63.92GB (52.57GB free)
VM: 0%
Screen Reader: no
Process Argv:
GPU Status: 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled

Powershell extension version: 1.10.2

[SydneyhSmith]

@carlos-ricciardi thanks for submitting this issue, we were able to re-pro it and will hopefully be able to start working on it soon.

[rkeithhill]

Looking at the diff between the tags 1.8.4 and 1.9.0, I couldn't see anything that should have broken this.

[carlos-ricciardi]

Sorry about the wrong info. It started in version 1.10.0. I couldn't repro in 1.9.0 either.

[rkeithhill]

Thanks for the update!

[rkeithhill]

Um yeah, those changes present a target rich environment for a breaking change in this area. We changed how we spin up the named pipes for debug to include different names for In/Out (read/write). Hmm, but in this case (according to the logs attached) we're using the older "NamedPipe" duplex pipe.

[TylerLeonhardt]

I've got a PR out to fix this. 👍 See ^