ole32: Add debug info to RunningObjectTable critical section.

So it's possible to easily debug deadlocks involving the Internal ROT object Signed-off-by: Lorenzo Ferrillo <lorenzofersteam@live.it>

ole32: Add debug info to RunningObjectTable critical section.
516f68b6 · Lorenzo Ferrillo · Alexandre Julliard · 7860dd06 · 516f68b6
Commit 516f68b6 authored Sep 10, 2023 by Lorenzo Ferrillo Committed by Alexandre Julliard Sep 11, 2023
Show whitespace changes
Inline Side-by-side

Showing with 10 additions and 1 deletion

moniker.c dlls/ole32/moniker.c +10 -1

No files found.
--- a/dlls/ole32/moniker.c
+++ b/dlls/ole32/moniker.c
@@ -707,10 +707,19 @@ static const IRunningObjectTableVtbl VT_RunningObjectTableImpl =
    RunningObjectTableImpl_EnumRunning
 };
+static RunningObjectTableImpl rot;
+static RTL_CRITICAL_SECTION_DEBUG critsect_debug =
+{
+    0, 0, &rot.lock,
+    { &critsect_debug.ProcessLocksList, &critsect_debug.ProcessLocksList },
+      0, 0, { (DWORD_PTR)(__FILE__ ": RunningObjectTable_section") }
+};
 static RunningObjectTableImpl rot =
 {
    .IRunningObjectTable_iface.lpVtbl = &VT_RunningObjectTableImpl,
-    .lock.LockCount = -1,
+    .lock = { &critsect_debug, -1, 0, 0, 0, 0 },
    .rot = LIST_INIT(rot.rot),
 };