Unable to debug .NET 5 application after upgrading to macOS Big Sur

[areller]

Description

Recently, I've upgraded my mac to macOS Big Sur, now, I'm no longer able to debug .NET applications via vscode.
Whenever I try to attach a debugger, I get this error

Unable to attach to CoreCLR. Unknown Error: 0x80131c3c

Configuration

I'm running .NET 5.0.100 on macOS Big Sur (Macbook 2017 Pro, Intel x64)
This happens with any .NET application

Regression?

I tried changing the target framework to netcoreapp3.1 and got the same error.

Other information

I read that some people have fixed a similar problem by downgrading XCode from v12 to v11, I tried it myself (downgraded to v11.7) but it didn't work

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

Recently, I've upgraded my mac to macOS Big Sur, now, I'm no longer able to debug .NET applications via vscode.
Whenever I try to attach a debugger, I get this error

Unable to attach to CoreCLR. Unknown Error: 0x80131c3c

Configuration

I'm running .NET 5.0.100 on macOS Big Sur (Macbook 2017 Pro, Intel x64)
This happens with any .NET application

Regression?

I tried changing the target framework to netcoreapp3.1 and got the same error.

Other information

I read that some people have fixed a similar problem by downgrading XCode from v12 to v11, I tried it myself (downgraded to v11.7) but it didn't work

Author:	areller
Assignees:	-
Labels:	area-Diagnostics-coreclr, untriaged
Milestone:	-

[tommcdon]

@hoyosjs

[hoyosjs]

This is a dupe of #42311. Closing in favor of that one.