[Bug 8514] getsockname
Wine Bugs
wine-bugs at winehq.org
Sat Jun 9 03:45:05 CDT 2007
http://bugs.winehq.org/show_bug.cgi?id=8514
------- Additional Comments From citizenr at gmail.com 2007-09-06 03:45 -------
I just did git fetch and noticed this in the sock.c code
/* test getsockname() to get peer's port */
ss = sizeof ( peer[i].addr );
ok ( getsockname ( peer[i].s, (struct sockaddr *) &peer[i].addr, &ss
) != SOCKET_ERROR, "UDP: could not getsockname()\n" );
ok ( peer[i].addr.sin_port != htons ( 0 ), "UDP: bind() did not
associate port\n" );
}
/* test getsockname() */
ok ( peer[0].addr.sin_port == htons ( SERVERPORT ), "UDP: getsockname
returned incorrect peer port\n" );
is second ok () is using the buggy wine behaviour? and if yes then why?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the wine-bugs
mailing list