Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger: The "stopAtEntry" property has no effect #1216

Closed
ClaireKang opened this issue Feb 10, 2017 · 1 comment
Closed

Debugger: The "stopAtEntry" property has no effect #1216

ClaireKang opened this issue Feb 10, 2017 · 1 comment
Labels

Comments

@ClaireKang
Copy link

ClaireKang commented Feb 10, 2017

Environment data

dotnet --info output:
VS Code version: 1.9.1
C# Extension version: 1.7.0
OS: Windows 10 Enterprise Insider Preview
Build: 15032.1000.AMD64FRE.RS_ONECORE_BASE_BPT1.170207-1700_CLIENT_ENTERPRISE_EN-US_VL.VHDX
Scenarios: WSL Pipe

Steps to reproduce

  1. Open attached folder
    app1.zip

  2. Change the configurations in launch.json (Pipe launch)
    "stopAtEntry": true,

  3. Copy the code from Windows with the command "cp /mnt/c/temp/app1/Program.cs ." in "Bash on Ubuntu on Windows" window.

  4. dotnet build.

  5. Select 'Pipe launch'.

  6. F5 to start debugging.

Expected behavior

Break at the first line of main.(int a=1).

Actual behavior

There is any line being hit while debugging.

##Investigation

  1. Change the configurations in launch.json (Pipe launch)
    "externalConsole": true,
    There is not occur the Console window.
  2. Expressions can output on debug console window.
  3. Could you please help me to confirm Enable tslint #1 is expected?
@rajkumar42
Copy link
Contributor

This is probably https://github.com/dotnet/coreclr/issues/8606, I'm closing this issue.

"externalConsole" for remote pipe, will not open up a new console.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants