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

OSX : Unable to attach to CoreCLR. #1348

Closed
ggregg opened this issue Mar 28, 2017 · 2 comments
Closed

OSX : Unable to attach to CoreCLR. #1348

ggregg opened this issue Mar 28, 2017 · 2 comments

Comments

@ggregg
Copy link

ggregg commented Mar 28, 2017

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.1)

Product Information:
Version: 1.0.1
Commit SHA-1 hash: 005db40cd1

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

VS Code version: 1.10.2 (1.10.2)
C# Extension version: 1.8.0

Notes

I installed last night the MacOS (10.12.4 (16E195)) and Xcode (8.3 (8E162)) updates and this morning the debugger no longer works. Thanks for help.

Steps to reproduce

In terminal

dotnet new console
dotnet restore

Open Visual Studio Code

Required assets to build and debug are missing from 'test'. Add them? Yes
Launch : .NET Core Launch (console)

The program '[3439] test.dll' has exited with code -1 (0xffffffff).

You may only use the Microsoft .NET Core Debugger (vsdbg) with...
Unable to attach to CoreCLR.

Expected behavior

Debugging :)

Actual behavior

No-debugger :(

@Tesjkh
Copy link

Tesjkh commented Mar 28, 2017

Same issue, I just updated to 10.12..
I hope this will be fixed quickly

@gregg-miskelly
Copy link
Contributor

This is a duplicate of #1220. I will fix the title of that bug to make it more clear.

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

No branches or pull requests

3 participants