X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Thomas Maier-Komor <thomas AT maier-komor DOT de>
Subject:	race on pipe causing read to erroneously return 0?
Date:	Sun, 24 Aug 2008 16:00:59 +0200
Lines:	12
Message-ID:	<g8rpir$a68$1@ger.gmane.org>
Mime-Version:	1.0
User-Agent:	Thunderbird 2.0.0.14 (X11/20080505)
X-IsSubscribed:	yes
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

Is it possible that there is somewhere a race condition in the
cygwin.dll that causes the reader on a named pipe getting a return value
of 0 from read, although another process has already opened the named
pipe for writing.

In consequence, in my application I see sporadic occurrences of SIGPIPE,
when my application closes the named pipe after getting 0 from read.

Any ideas?

TIA,
Thomas


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

- Raw text -