From: Tom McDonald Date: Thu, 10 Aug 2023 01:39:00 +0000 (-0400) Subject: Debugger IPC creation failure should not abort coreclr startup (#90161) X-Git-Tag: accepted/tizen/unified/riscv/20231226.055536~397 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3b21b909f47ee07ec7f4cad0edde5404ebd85dd2;p=platform%2Fupstream%2Fdotnet%2Fruntime.git Debugger IPC creation failure should not abort coreclr startup (#90161) * Debugger IPC creation failure should not abort coreclr startup * Add log message for debugger pipe init failure * Use Stress log instead of COMPLUS logging --- diff --git a/src/coreclr/debug/ee/debugger.cpp b/src/coreclr/debug/ee/debugger.cpp index 0372768..a44a9e2 100644 --- a/src/coreclr/debug/ee/debugger.cpp +++ b/src/coreclr/debug/ee/debugger.cpp @@ -1947,7 +1947,8 @@ HRESULT Debugger::Startup(void) if (FAILED(hr)) { ShutdownTransport(); - ThrowHR(hr); + STRESS_LOG0(LF_CORDB, LL_ERROR, "D::S: The debugger pipe failed to initialize in /tmp or $TMPDIR.\n"); + return S_OK; // we do not want debugger IPC to block runtime initialization } #endif // FEATURE_DBGIPC_TRANSPORT_VM