Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 9 Dec 2000 14:17:18 -0500 (EST) From: Dave Johnson To: cygwin@cygwin.com Subject: getsockname() doesn't fill out data after non-blocking connect() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII While porting an application to cygwin I've discovered the following: After a non-blocking connect() is called for a TCP connection I am calling getsockname() to determine the IP on the local size of the connection attempt. After calling getsockname() and getting the IP address from .sin_addr.s_addr of the sockaddr_in structure the IP was filled out with 0's instead of the IP address of the interface in which the connection attempt is going out on. Doing another getsockname() after the socket becomes writable and the connection is completed returns valid data. Other UNIX OS's will return valid socket information after a non-blocking connect(). Is this a limitation of cygwin or a bug? This is with cygwin 1.1.4 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com