diagnostics: Process XXX not running compatible .NET Core runtime

I have tried to use both projects .NET Core 3.1 and 3.0. Installed the latest tool with dotnet tool install -g dotnet-dump but it did not find my process and was unable to dump it. I have installed even both SDKs and Runtimes of 3.0 and 3.1 just for that but seems like did not work. Tried updating tool as well.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 5
Comments: 29 (11 by maintainers)

Most upvoted comments

Core dump generation FAILED 0x80004005

IvMisticos on Mar 28, 2020

My bad, the environment file got truncated from copying from the vim buffer.

COMPlus_StressLog=1
COMPlus_StressLogSize=200000
COMPlus_TotalStressLogSize=4000000
COMPlus_LogFacility=1000
COMPlus_LogLevel=4

However, that wouldn’t have shown us the issue. The issue here is the usage of PrivateTmp=true. This means managed debugging as all these diagnostic features won’t work as we rely on being able to access tmp. While we understand the desire to use PrivateTmp in a locked down secure scenario, we currently don’t support this. Is it possible to remove the private tmp usage?

hoyosjs on Mar 27, 2020