https://bugs.winehq.org/show_bug.cgi?id=41562
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #5 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Bruno Jesus from comment #4)
trace:winsock:WS2_recv_base socket 0458, wsabuf 0x804de48, nbufs 1, flags 0, from (nil), fromlen -1, ovl (nil), func (nil) trace:winsock:WS2_recv_base fd=129, options=0 trace:winsock:WS2_recv_base -> 32768 bytes trace:winsock:WS2_recv_base socket 0458, wsabuf 0x804de48, nbufs 1, flags 0, from (nil), fromlen -1, ovl (nil), func (nil) trace:winsock:WS2_recv_base fd=129, options=0 trace:winsock:WS2_recv_base -> 32768 bytes trace:winsock:WS2_recv_base socket 0458, wsabuf 0x804de48, nbufs 1, flags 0, from (nil), fromlen -1, ovl (nil), func (nil) trace:winsock:WS2_recv_base fd=129, options=0 trace:winsock:DllMain 0x7c100000 0x2 (nil) warn:winsock:wsaErrno errno 14, (Błędny adres). warn:winsock:WS2_recv_base -> ERROR 10014
Everything goes fine until suddenly a WSAEFAULT happens during (probably) a recvmsg call.
Reminds me of https://bugs.winehq.org/show_bug.cgi?id=37669. Does the following staging patchset help? https://github.com/wine-compholio/wine-staging/tree/master/patches/ws2_32-Wr...