Debugger: Breakpoints cannot be set when the target app is in a tight loop

[v-zhanme]

Environment data

dotnet --info output:
VS Code version: 1.7.1
C# Extension version: v.1.5.0-beta7
.NET Core version: 1.0.0-SDK Preview4
C# Extension version:

Steps to reproduce

Launch the project in Command Prompt(cmd window) using the Command 'dotnet run'.
2.Open the attachment project with VSCode.
myapp.zip

3.change the debugger status is .NET Core Launch(console)
4.Press F5 to start debugging
5.set a BP at line 17

Expected behavior

The cursor will hit line 17

Actual behavior

Can not hit BP at line 17

[gregg-miskelly]

@v-zhanme Your code has an infinite loop, so line 17 will never execute. Is there something I am missing?

[v-zhanme]

I'm sorry for typo, The BP should be on line 9

[gregg-miskelly]

@v-zhanme Thanks. What OS were you on?

[v-zhanme]

This issue repro on Mac and Fedora. And not repro on windows OS.
I send e-mail to you about this question at last an hour.

[gregg-miskelly]

This issue only repos if the app is in a tight loop. @mikem8361 would it make sense to have a bug in the CoreCLR repo about breaking into apps on Unix when the app is in a tight loop? Or is that just a really hard problem and I should resolve this as 'by design'.

[mikem8361]

It is similar to https://github.com/dotnet/coreclr/issues/4623 which is about aborting funcevals that are caught in a tight loop. The reason and the solution for both problems would be the same. This is a fairly large work item.

[gregg-miskelly]

Resolving this as external.