Re: Using recvmsg() with non-unicast datagram (UDP) socket: inconsistent results

2012-08-01 Thread Corinna Vinschen
On Aug 1 14:35, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: > > 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 snap

RE: Using recvmsg() with non-unicast datagram (UDP) socket: inconsistent results

2012-08-01 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C]
> 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/snapsh

Re: Using recvmsg() with non-unicast datagram (UDP) socket: inconsistent results

2012-08-01 Thread Corinna Vinschen
On Jul 31 12:43, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: > Hi, > > Observed is an inconsistent result when recvmsg() is used on a > UDP socket with or without ancillary control message parameters. > > Here's is an example: > > static char buf[1 << 16]; > struct sockaddr_in sin; >