On Do, 2009-08-20 at 18:22 +0200, Alexandre Julliard wrote:
Juan Lang juan.lang@gmail.com writes:
There can be several other ways to handle this, it needs test cases to determine which way Windows is using.
Sorry for my lack of imagination: could you suggest at least one other way so I can make sure the tests are representative?
It may check for just 0xffffffff as a special case, or check for high word being 0 or 0xffff and rejecting others, etc. Some values to test would be things like 0x1234ffff, 0x12340000, 0xffff0000, etc.
Jeff did a patch in the bug, which check for SOCKET_ERROR, when setsockopt was called with 0xffffffff as level: http://bugs2.winehq.org/attachment.cgi?id=20211
I'm offline tomorrow, otherwise i woud add more tests to my old patch.