X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.0 required=5.0	tests=BAYES_20
X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: 1.7.7 blocking socket problem
Date: Wed, 17 Nov 2010 11:20:22 -0600
Message-ID: <DC0D3CA127373142BB40E5C6FA63B4D102ABEEE7@CARSMAIL1.CARS.APS.ANL.GOV>
From: "Mark Rivers" <rivers AT cars DOT uchicago DOT edu>
To: <cygwin AT cygwin DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

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().

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.  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.  I did
look through the mailing list archives and did not see anything.

This problem occurs on every Cygwin system it has been tested on (more
than 6), so it is not restricted to particular hardware.  All systems
are running Windows XP SP3 I believe.

Thanks very much,
Mark Rivers


--
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