Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Thu, 20 Feb 2003 18:14:00 +0100 From: Corinna Vinschen To: cygwin-developers AT cygwin DOT com Subject: Re: Threaded socket hang in 1.3.20 Message-ID: <20030220171400.GE1403@cygbert.vinschen.de> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20030218222746 DOT GD2404 AT tishler DOT net> <20030220141539 DOT GE2467 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030220141539.GE2467@cygbert.vinschen.de> User-Agent: Mutt/1.4i On Thu, Feb 20, 2003 at 03:15:39PM +0100, Corinna Vinschen wrote: > Now back to the test case. With these changes the socket() call doesn't > hang but now connect() is in trouble. It hangs for a while until it > returns with error 116, Connection timeout. > > I must admit, that I didn't find the cause so far. Help in debugging > this is appreciated. Aaaaarrrrghh! I found it. Cockpit error. Change this: lsocket.sin_addr.s_addr = INADDR_LOOPBACK; to lsocket.sin_addr.s_addr = htonl(INADDR_LOOPBACK); Pooh, I'm glad that this wasn't a Cygwin problem. I wouldn't have known how to track that down. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.