-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In Wine 3.0 NtWaitForKeyedEvent()
does not accept null handles
#36
Comments
This is contingent on the opinion of Wine people on https://bugs.winehq.org/show_bug.cgi?id=44620. |
@lhmouse I also wrote this in the bug report, but thought it might be good to post it here too. This seems to be fixed by: https://source.winehq.org/git/wine.git/commit/a0050be13f77d364609306efb815ff8502e332ee At least the testcase attached to that bug works now, could you test if it fixes this issue too? |
@gverm Thank you I will keep an eye on this. I don't build Wine myself so I have to wait for an unstable development version available from winehq. |
I can confirm this has been fixed on the following version:
Thanks for your work! |
... in which case it fails with
0xc0000008
(STATUS_INVALID_HANDLE
).On Windows 7 if the handle is null, the global keyed event with the name
\KernelObjects\CritSecOutOfMemoryEvent
is used. Since this is not the case for Wine, a handle has to be opened explicitly at lease once per process. It must not be closed thereafter, unless as a result of process exit of course.The text was updated successfully, but these errors were encountered: