Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Do not create diagnostics server thread and pipe if EnableDiagnostics is set to 0#27137

Merged
sywhang merged 2 commits intodotnet:masterfrom
sywhang:dev/suwhang/27314
Oct 11, 2019
Merged

Do not create diagnostics server thread and pipe if EnableDiagnostics is set to 0#27137
sywhang merged 2 commits intodotnet:masterfrom
sywhang:dev/suwhang/27314

Conversation

@sywhang
Copy link

@sywhang sywhang commented Oct 11, 2019

We already have the environment variable COMPlus_EnableDiagnostics that disables the debugger when it is set to 0. We should disable diagnostics server as well if this environment variable is set to 0.

This fixes https://github.com/dotnet/coreclr/issues/27134.

Copy link
Member

@noahfalk noahfalk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@sywhang sywhang merged commit c2afcec into dotnet:master Oct 11, 2019
sywhang added a commit to sywhang/coreclr that referenced this pull request Oct 11, 2019
… is set to 0 (dotnet#27137)

* Do not create diagnostics server thread and pipe if EnableDiagnostics is set to 0

* Remove unnecessary check for config var in DiagnosticServer::Shutdown
sywhang added a commit that referenced this pull request Oct 15, 2019
… is set to 0 (#27137) (#27140)

* Do not create diagnostics server thread and pipe if EnableDiagnostics is set to 0

* Remove unnecessary check for config var in DiagnosticServer::Shutdown
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a runtime configuration to disable diagnostics server

4 participants