[Bug 14831] ws2_32: sock.ok fails in Solaris, but not Linux
wine-bugs at winehq.org
wine-bugs at winehq.org
Sat Aug 3 13:06:14 CDT 2019
https://bugs.winehq.org/show_bug.cgi?id=14831
Damjan Jovanovic <damjan.jov at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |damjan.jov at gmail.com
--- Comment #11 from Damjan Jovanovic <damjan.jov at gmail.com> ---
The winsock tests are actually really elaborate, and test the network stack so
thoroughly that they reveal differences between *nix network stacks.
For example, for FreeBSD 11.2:
sock.c:2509: Test failed: Expected 10044, received 10041
The different error is reported by FreeBSD's network stack for invalid socket()
parameters.
sock.c:6689: Test failed: WSASendMsg should have failed
FreeBSD allows unconnected TCP sockets to successfully sendmsg() data!
Windows and Linux don't.
sock.c:7275: Test failed: fdWrite socket events incorrect
Probably a regression in FreeBSD, where closing a socket doesn't get poll() to
report POLLHUP on the socket on the other end:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227259
I think they fixed it in a newer version of FreeBSD.
and lots more :(
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list