.NET 5.0.100/101 remote Raspberry debugging doesn't work

[myg3l]

"Unable to attach to CoreCLR. Unknown Error: 0x80131c4f".

Appears to be some .Net 5.0.100 runtime or debugger issue. Workaround by using 3.1.404 on rpi & host

dotnet/vscode-csharp#4210

[jefflill]

.NET 5 worked OK during my testing debugging remotely on a Raspberry. Have you tried the Raspberry Debugger and seen a failure? At this point, I'm probably the only person to actually use the thing.

[myg3l]

I've also used the https://github.com/radutomy/VSRemoteDebugger

Both VSRemoteDebugger and Raspberry Debugger fails with the .NET 5.0.100 for me. Both works if I revert to the .Net Core v3.1(.404).

I'm to lazy to work with VS Code so think these remote debuggers are a great idea :)

[jefflill]

I agree, VS Code is OK but I'm used to Visual Studio and I have multiple monitors so I want to have multiple windows open.

I'll try to replicate this and I've bugged a friend to try it too. I wonder perhaps if I need to deploy a different version of VSDBG to the Raspberry.

[jefflill]

Looks like the .NET runtime team is tracking this here:

dotnet/runtime#44745

[jefflill]

I've been able to replicate this now for Raspberry Debugger too. I missed this in my early testing because the project was still targeting .NET Core and a .NET Core 3,1 SDK was already installed on the Raspberry.

#16 .NET Core SDK not installed on Raspberry when .NET 5 SDK is installed on workstation

was also preventing folks from downgrading to .NET Core 3.1.x because the debugger wouldn't install a .NET Core 3.1 SDK due to a misunderstanding about how dotnet --info works. This is corrected now.

---

So, this is still a bug that the .NET Runtime folks will have to fix: dotnet/runtime#44745. Hopefully this will work again when MSFT publishes the next .NET 5 SDK. I'll keep this issue open as a reminder to check for a new SDK.

...at least you can downgrade to .NET 3.1 now and use the Raspberry Debugger

[jefflill]

The .NET folks have been able to reproduce this now and are working on a fix. The problem looks like it might be constrained to Raspberry's with more than 2 GiB RAM.

dotnet/runtime#44745

[jefflill]

I noticed that .NET 5.0.1 has been released but it doesn't include a fix for dotnet/runtime#44745