https://bugs.winehq.org/show_bug.cgi?id=50990
--- Comment #10 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to msdobrescu from comment #8)
Is there a way to assess the crash cause? Is it possible to have an unhandled return value due to incorrect/unexpected return value or values from the Windows SDK perspective, like a NULL instead an empty string or other?
What do we miss in the debug logs? Could that be a different component that also returns the wrong value?
Potentially it might be anything. Someone needs to debug this, and remote debugging is not an option.