Step-Over does not returns until i press a key inside the terminal on Ubuntu
See original GitHub issueSystem Details
- 
Operating system name and version: Ubuntu 16.04 (current LTS fresh installed) + Ubuntu Desktop
 - 
VS Code version: Version 1.12.2 Date 2017-05-10T13:16:25.899Z Shell 1.6.6 Renderer 56.0.2924.87 Node 7.4.0
 - 
PowerShell extension version: 1.2.1
 - 
Output from
$PSVersionTable: PSVersion 6.0.0-beta
PSEdition Core
BuildVersion 3.0.0.0
CLRVersion
GitCommitId v6.0.0-beta.1
OS Linux 4.4.0-78-generic #99-Ubun… Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0 
Issue Description
using F10 (Step-Over) to execute a line, the execution seems to hang/never returns! workaround: set cursor into the terminal and press (any) key: Step-Over comes back and the execution cursor is on the next line… work can be continued.
Observations: the bahavior is not on every line, it seems specially if Write-XXX commands are involved
i’m new on Linux so i’m not sure that i’m doing everything in the right way… regards Werner
Issue Analytics
- State:
 - Created 6 years ago
 - Comments:12
 

Top Related StackOverflow Question
Sorry, I haven’t given up on this bug yet. Just had to wrestle with some other bugs for the upcoming 1.5.1 release. I plan to spend time on this one over the weekend to see if there’s a way to get this working. I’d like to get this in for 1.5.1. We’ll see how it goes.
Hi @WernerMairl, I don’t actively develop the code for this project, and I don’t work at Microsoft either, however I do help to curate issues on this project. Unfortunately, time doesn’t presently allow me to dive deep in this particular area.
For the time being, since it seems you’re interested in helping to drive a root cause analysis and resolution, I would suggest that you capture the verbose logs from the VSCode PowerShell extension. You can probably get started by reviewing those logs for anomalies, such as errors or warnings. David would be much better versed in reading these logs than I would be. Check out the README.md in the root of this GitHub project for directions to enable verbose logging, and where to find the log files on your Linux filesystem.