From 3b21b909f47ee07ec7f4cad0edde5404ebd85dd2 Mon Sep 17 00:00:00 2001
From: Tom McDonald <tommcdon@microsoft.com>
Date: Wed, 9 Aug 2023 21:39:00 -0400
Subject: [PATCH] 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
---
 src/coreclr/debug/ee/debugger.cpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/coreclr/debug/ee/debugger.cpp b/src/coreclr/debug/ee/debugger.cpp
index 0372768be2899..a44a9e235f36c 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