Run Debug stalls after build task

Environment data

dotnet --info output:

.NET Command Line Tools (2.0.3)

Product Information:
 Version:            2.0.3
 Commit SHA-1 hash:  eb1d5ee318

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.13
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.0.3/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.3
  Build    : a9190d4a75f4a982ae4b4fa8d1a24526566c69df

VS Code version: 1.18.1 C# Extension version: 1.13.1

Steps to reproduce

dotnet new console -o test-debug
cd test-debug
code .

put a breakpoint on line 9. Run Debug.

Expected behavior

The debugger should launch and hit the breakpoint, showing current runtime variables.

Actual behavior

The build task run successfully, but the debugger variables never show up. It looks like something is hanging because the spinner in the lower left corner is spinning. Even after tens of minutes, the debugger never fully launches.

Omnisharp Logs: omnisharp test debug.txt

Work arounds:

1. Use VS Code from the Insiders Channel (download link) -or-
2. Edit your launch.json and comment out the “preLaunchTask”: “build” line. If you do this you will now need to build from the command line (project will not automatically rebuild as part of start debugging). -or-
3. At the end of the build, put focus on the terminal and hit enter

[gregg-miskelly]

Here is the VS Code issue: https://github.com/Microsoft/vscode/issues/37846

[gregg-miskelly]

I updated my Mac to the latest of everything (VS Code, CLI, OS) and I can also reproduce this problem.

It looks like a VS Code issue – VS Code thinks the build task didn’t finish even though it did. I tried the VS Code Insiders channel and the problem went away, so I am guessing this is something that they have already fixed.

So I believe there are three possible work around:

1. Install Insiders Channel -or-
2. Edit your launch.json and comment out the "preLaunchTask": "build" line. If you do this you will now need to build from the command line (project will not automatically rebuild as part of start debugging). -or-
3. Go to the terminal and hit the enter key at the end of the build