Re: [PATCH 0/2] MR3372: ole32: Leave the RunningObjectTable Critical Section before unmarshalling object stream

[Lorenzo Ferrillo (＠llde)]

Hi @nsivov. Doesn't most of wine Critical section use debug infos, even other ole32 CS? Why would this one be different? Or you meant something else (the struct change maybe)?

Also before commit 48bd5461ed0d5ba0e7c7e0c5ae5fb782764b2003  ole32: Use single static instance for ROT.
this CS did have debug information.
If the issue is about the structure change, maybe I can remove it.
Understanding the flow that caused this deadlock for VS2019  was quite hard without this debug info, in fact I wasn't sure this was actually IROT related before adding this info for testing.