Why 0.1.0.0 as local socket address instead of 127.0.0.1?

[Bruno Jesus]

On Fri, Jan 25, 2013 at 4:11 PM, Francois Gouget
<fgouget at codeweavers.com> wrote:
>
> The ws2_32:sock fails on some of my machines with the following error:
>
> sock.c:4794: Test failed: Local socket address is different 0.1.0.0 != 127.0.0.1
>
> Does anyone know why we GetAcceptExSockaddrs() would return 0.1.0.0
> instead of 127.0.0.1? Looking at the Windows 7 winetest results it does
> not appear to be correlated with either the SP1 or IE9.
>
> For instance got an error on Windows 7 + SP1 + IE9 (32 and 64-bit):
> http://test.winehq.org/data/b233d2054e64e216a5b3868f301bfc934b019b4b/win7_fg-win7u64-1spie9/ws2_32:sock.html
> http://test.winehq.org/data/b233d2054e64e216a5b3868f301bfc934b019b4b/win7_fg-win7u64-1spie9t64/ws2_32:sock.html
>
> But not here (Windows 7 + SP1 + IE9 64-bit):
> http://test.winehq.org/data/83846cd131aac33228bf08aefae0bf0ea93d4273/win7_fg-win7u64-1spie9t64/ws2_32:sock.html
>
> I also got it failing at least once on a Windows 2000 SP4 VM:
> http://test.winehq.org/data/b233d2054e64e216a5b3868f301bfc934b019b4b/2000_fg-win2000-4sp/ws2_32:sock.html
>
> But never saw it fail on my Windows XP or 2003 VMs.

I don't know the answer yet, I'll add a more verbose debug of the
struct, add Set/GetLastError and check the returned pointers. I have a
win7 machine that does not reproduce the issue, so I'll try installing
SP1 + IE9 hoping to break things and expose the test failure.

> --
> Francois Gouget <fgouget at codeweavers.com>
>

Best wishes,
Bruno