-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
DOTNET_ vs COMPlus_ env var prefix for creating dumps #58924
Comments
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. |
Tagging subscribers to this area: @tommcdon Issue DetailsBased on this docs: https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dumps the environment variable Running in
|
This should've started working with #50507, not sure why it didn't. Regardless we should amend the public docs to at least state this is only a 6.0+ feature. |
Turns our this is handled in the procabort handler which is in the PAL. Such layer doesn't have the CLR's config facility, so we do a hard manual check: runtime/src/coreclr/pal/src/thread/process.cpp Lines 3278 to 3297 in 331823f
Affected variables:
|
That is documented. Unfortunately it seems some of the official variables do their own thing – this is unfortunate. This isn't a .NET 6 issue really so we can move this to .NET 7 for now. |
Based on this docs: https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dumps the environment variable
DOTNET_DbgEnableMiniDump
should work the same way asCOMPlus_DbgEnableMiniDump
.However, the former (DOTNET_...) didn't work for me and the latter (COMPlus_) did. Is the documentation wrong or is this a bug/missing feature?
Running in
mcr.microsoft.com/dotnet/nightly/sdk:6.0-bullseye-slim
docker image:The text was updated successfully, but these errors were encountered: