Re: [4/4] ws2_32: Avoid a crash with an optional pointer in WSAAsyncGetServByName.

2011-06-03 Thread Andrew Nguyen
On 06/01/2011 11:09 AM, Alexandre Julliard wrote: Andrew Nguyen angu...@codeweavers.com writes: On 06/01/2011 07:39 AM, Marvin wrote: === WXPPROSP3 (32 bit sock) === sock.c:501: Test failed: oob_server (218): unexpectedly at the OOB mark: 0 sock.c:511: Test failed: oob_server (218):

Re: [4/4] ws2_32: Avoid a crash with an optional pointer in WSAAsyncGetServByName.

2011-06-01 Thread 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 http://testbot.winehq.org/JobDetails.pl?Key=11362 Your paranoid

Re: [4/4] ws2_32: Avoid a crash with an optional pointer in WSAAsyncGetServByName.

2011-06-01 Thread Andrew Nguyen
On 06/01/2011 07:39 AM, Marvin wrote: 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

Re: [4/4] ws2_32: Avoid a crash with an optional pointer in WSAAsyncGetServByName.

2011-06-01 Thread Alexandre Julliard
Andrew Nguyen angu...@codeweavers.com writes: On 06/01/2011 07:39 AM, Marvin wrote: === WXPPROSP3 (32 bit sock) === sock.c:501: Test failed: oob_server (218): unexpectedly at the OOB mark: 0 sock.c:511: Test failed: oob_server (218): unexpectedly at the OOB mark: 0 The test failure is not