Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Fri, 30 Sep 2005 12:45:07 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: on the road to 1.5.19 - snapshot testing needed In-Reply-To: <20050929231320.GA13715@trixie.casa.cgf.cx> Message-ID: References: <20050929231320 DOT GA13715 AT trixie DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes On Thu, 29 Sep 2005, Christopher Faylor wrote: > So, once again, I'd like to finally release this thing and so I'm asking > for testing help. You all should know the drill by now but, just in case > you don't: This isn't a recent regression, and it may not even be supported, but I thought I'd report it. I'm also working on a STC, but just in case the description is good enough to get it fixed... When doing a fork/exec of a non-cygwin process and subsequently sending it a signal (I know, probably not supported) the cygwin stub process receives the signal (confirmed by strace), but it tries to call the handler previously installed by the parent process (if there was one, and in my case there was) instead of doing the SIG_DFL action (in this case, exiting). The result is that the process does not exit and hangs (both the stub and the non-cygwin process). If this isn't enough, please respond with "not enough info" and I'll supply the STC, cygcheck, etc. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/