X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B315820.4010602@gmail.com> Date: Tue, 22 Dec 2009 23:37:04 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: select() and named pipes References: <20091222224309 DOT GA3504 AT GIOVE> In-Reply-To: <20091222224309.GA3504@GIOVE> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Enrico Forestieri wrote: > I am experiencing a problem with select() and named pipes in cygwin 1.7. > The attached test case segfaults on the select() call, but works fine > with both cygwin 1.5 and linux. Confirmed. It appears that start_thread_pipe() is called for both pipes and fifos, but only for pipes is there a device_specific_pipe in the select_pipe_info struct passed in; for fifos this pointer is null. This is down to the different initialisation sequences in fhandler_pipe::except_* vs. fhandler_fifo::except_*. I'm not sure if this is an omission in the except_* functions or an oversight in the start_thread_pipe function; cgf will know what to do. cheers, DaveK -- 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