Re: ws2_32: Fix some edge cases for getaddrinfo in BSD and OSX

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=4901

Your paranoid android.


=== wxppro (32 bit sock) ===
sock.c:557: Test failed: oob_server (b34): unexpectedly at the OOB mark: 0

=== wvistau64 (32 bit sock) ===
sock.c:557: Test failed: oob_server (744): unexpectedly at the OOB mark: 0
sock: unhandled exception c0000005 at 753E9799

=== w2008s64 (32 bit sock) ===
sock.c:547: Test failed: oob_server (768): unexpectedly at the OOB mark: 0
sock.c:557: Test failed: oob_server (768): unexpectedly at the OOB mark: 0
sock: unhandled exception c0000005 at 757C9799

=== wvistau64 (64 bit sock) ===
sock.c:557: Test failed: oob_server (b5c): unexpectedly at the OOB mark: 0

=== w2008s64 (64 bit sock) ===
sock.c:557: Test failed: oob_server (750): unexpectedly at the OOB mark: 0

=== w7pro64 (64 bit sock) ===
sock.c:547: Test failed: oob_server (a54): unexpectedly at the OOB mark: 0
sock.c:557: Test failed: oob_server (a54): unexpectedly at the OOB mark: 0
sock.c:326: Test failed: do_synchronous_recv (a54): error 10054:
sock.c:572: Test failed: oob_server (a54): not at the OOB mark: 1