question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fedora 28: Unable to attach to CoreCLR

See original GitHub issue

Environment data

dotnet --info output:

$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   2.1.403
 Commit:    04e15494b6

Runtime Environment:
 OS Name:     fedora
 OS Version:  28
 OS Platform: Linux
 RID:         fedora.28-x64
 Base Path:   /usr/share/dotnet/sdk/2.1.403/

Host (useful for support):
  Version: 2.1.5
  Commit:  290303f510

.NET Core SDKs installed:
  2.1.403 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.5 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.5 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.5 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

VS Code version:

Version: 1.25.1
Commit: 1dfc5e557209371715f655691b1235b6b26a06be
Date: 2018-07-11T15:40:20.190Z
Electron: 1.7.12
Chrome: 58.0.3029.110
Node.js: 7.9.0
V8: 5.8.283.38
Architecture: x64

C# Extension version:

1.15.2

Steps to reproduce

I follow this document to build a sample dotnet project: https://www.microsoft.com/net/learn/dotnet/hello-world-tutorial. Then I set a break point at Console.WriteLine("Hello World!");.

Expected behavior

Debugging 😃

Actual behavior

Error message:

-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
Unable to attach to CoreCLR.

Help is appreciated.

Thank you.

/Henrik

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:10 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
walkjiveflycommented, Nov 30, 2018

Debugging works for me with Razor 1.17.1 installed and without it being disabled.

But @HenrikBach1 In VSCode File/Preferences/Settings gets me here: image

0reactions
HenrikBach1commented, Dec 3, 2018

@NTaylorMullen,

That explains a lot.

I’ll try to bump up to version 1.17, then.

Thank you.

/Henrik

Read more comments on GitHub >

github_iconTop Results From Across the Web

"Unable to attach to CoreCLR" when debugging a ...
I have an old .NET5 project that I was testing upgrade to .NET6. I was able to build and debug .NET5 project using...
Read more >
Failed attaching debugger to local docker linux container from ...
The problem is when I tried to attach debugger from vs2019 using Debug -> Attach to Process -> ConnectionType Docker(Linux Container) ...
Read more >
vscode Unable to attach to CoreCLR. Access is denied
具体是360杀毒软件阻止了调试debugging的运行,关闭杀毒软件,可以顺利调试Debugging。 参考. 无法附加到CoreCLR。拒绝访问 .net core控制台无法附加到clr.
Read more >
Let's debug the Core CLR with WinDBG! - Medium
This post of the series shows how we debugged the Core CLR to figure out insane contention duration. Part 1: Replace .
Read more >
Visual Studio Code remote debugging of a .Net Core ... - jenx.si
Net Core application running on Raspberry Pi and Ubuntu Linux ... I need to tune up Visual Studio Code to able to attach...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found