Using recvmsg() with non-unicast datagram (UDP) socket: inconsistent results
Lavrentiev, Anton (NIH/NLM/NCBI) [C]
lavr@ncbi.nlm.nih.gov
Wed Aug 1 18:45:00 GMT 2012
> I applied a patch which should fix this problem. It always uses
> WSARecvMsg now, if called from recvmsg, still provided it is possible,
> of course (No SOCK_STREAM, no AF_LOCAL).
>
> I'm just generating a new developer snapshot. Please give the today's
> snapshot from http://cygwin.com/snapshots/ a try. Should be up in
> about
> half an hour.
The patched DLL now returns consistent msg_flags regardless of whether
or not the control message has been requested. Thanks!
Could I ask for another favor that since the native WSA msg_flags get
propagated to the CYGWIN environment, the definitions for the additional
flag bits, MSG_MCAST and MSG_BCAST (as defined by WSA) to be added to
<cygwin/socket.h> please?
http://msdn.microsoft.com/en-us/library/windows/desktop/ms741645%28v=vs.85%29.aspx
Anton Lavrentiev
Contractor NIH/NLM/NCBI
More information about the Cygwin
mailing list