Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: 8 Nov 2001 12:24:49 -0500
Message-ID: <20011108172449.22627.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin-developers AT cygwin DOT com
In-reply-to: <20011108120956.A2730@redhat.com> (message from Christopher
	Faylor on Thu, 8 Nov 2001 12:09:56 -0500)
Subject: Re: Debugging problem in peek_pipe in select.cc
References: <20011108155542 DOT 19905 DOT qmail AT lizard DOT curl DOT com> <20011108120956 DOT A2730 AT redhat DOT com>

>  Date: Thu, 8 Nov 2001 12:09:56 -0500
>  From: Christopher Faylor <cgf AT redhat DOT com>
>  
>  The point of my addition of a mutex to peek_pipe was to prevent occurrences
>  of PeekNamedPipe blocking, actually.  It can block in pathological situations
>  when another thread/process is doing a blocking read.

Ah, so the MSDN documentation is wrong.

Imagine my surprise :-).

Is it actually documented somewhere else, where I didn't look, that
PeekNamedPipe can block, or did you just have to figure this out by
hard experience?

>  If you are still seeing hangs in the most recent sources, then there is
>  still some kind of race with the guard mutex in peek_pipe.  That is
>  where you will need to investigate.

OK, I'll update my sources and see if I can get it to happen again.

Thanks,

  jik