http://bugs.winehq.org/show_bug.cgi?id=13964
Summary: small .NET cmd util: CoWaitForMultipleHandles Unexpected wait termination Product: Wine Version: 1.0-rc5 Platform: PC-x86-64 URL: http://sourceforge.net/projects/outmodedbonsai/ OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ole AssignedTo: wine-bugs@winehq.org ReportedBy: htl10@users.sourceforge.net
Created an attachment (id=14126) --> (http://bugs.winehq.org/attachment.cgi?id=14126) C# source code of the little program
I have a very small C# program which just reads a .NET assembly dll, then uses the .NET reflection API to query the dll's version, then write it out to the console. (it is just a .NET dll version checking tool, basically).
It works with mono on linux, and it works with win32 mono on wine; but with microsoft .NET Framework under wine, (i.e. running it "plain" rather than through win32 mono, if one has both mono and .net framework 2.0 installed), it dies with a few thousands of "err:ole:CoWaitForMultipleHandles Unexpected wait termination: -1, 87" among other messages which scrolls off screen. I have seens the CoWaitForMultipleHandles message under completely different contexts (http://bugs.winehq.org/show_bug.cgi?id=12259#c2)
This seems to be related to how the .Net Framework interacts with wine, since the executable in both mono linux and win32 mono +wine work as expected.
The source code of the small C# program is attached. I can provide a small executable if it helps - the small C# program is a stripped down version of BeanSprout in the sourceforge project (and I am the project admin, so I can upload it there).
I know some might say this is not worth the time since it works with mono/linux win32 mono/wine, but I have other .NET programs which works poorly with either, and works better with MS.Net but only occasionally dies with a similiar message with MS.Net... and the thousands of "err:ole:CoWaitForMultipleHandles" messages also seems to bug other people (bug 12259, and possibly others).