X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 17 Nov 2010 18:50:42 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.7 blocking socket problem
Message-ID: <20101117175042.GE11144@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <DC0D3CA127373142BB40E5C6FA63B4D102ABEEE7 AT CARSMAIL1 DOT CARS DOT APS DOT ANL DOT GOV>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <DC0D3CA127373142BB40E5C6FA63B4D102ABEEE7@CARSMAIL1.CARS.APS.ANL.GOV>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Nov 17 11:20, Mark Rivers wrote:
> Folks,
> 
> I believe I have discovered a problem with blocking sockets on Cygwin.
> The problem is that very rarely a call to send() will never return.
> 
> I am having problem when using the Channel Access TCP/IP protocol in the
> EPICS control system (http://www.aps.anl.gov/epics/).
> 
> I have isolated the problem to a call to send() on the server which
> never returns.  This problem happens with a large number of well-tested
> clients, running on both Linux and Windows.  I can build the same EPICS
> server without Cygwin, using the MS VC++ Windows compiler and libraries
> and it does not fail.  When the call to send() hangs it is sending a
> large packet (just over 8KB).  The failure rate is very low, perhaps
> once in 10 million calls to send().

Wow, that's not very often.  You missed all the stuff from
http://cygwin.com/problems.html, so we don't know what Cygwin release
you're talking about.  If it's Cygwin 1.5, you're out of luck since we
don't support that anymore.  Otherwise...

> I realize that my application is difficult to reproduce for the Cygwin
> developers.  I am willing to try to write a simple socket server and
> client to try to reproduce the problem in a simple test setup. 

...that would be most helpful.

> But
> before I do that I would like to first know if there is a known problem
> of this sort that has already been reported, and perhaps fixed.

No, not really.  I wouldn't claim that Cygwin's socket implementation is
bug free, but this kind of very occassional hang is new to me.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple