Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Fri, 30 Sep 2005 19:34:58 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: on the road to 1.5.19 - snapshot testing needed
Message-ID: <20050930233458.GB29482@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20050929231320 DOT GA13715 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT CYG DOT 4 DOT 58 DOT 0509301237400 DOT 1904 AT PC1163-8460-XP DOT flightsafety DOT com> <Pine DOT CYG DOT 4 DOT 58 DOT 0509301705470 DOT 1904 AT PC1163-8460-XP DOT flightsafety DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.CYG.4.58.0509301705470.1904@PC1163-8460-XP.flightsafety.com>
User-Agent: Mutt/1.5.8i

On Fri, Sep 30, 2005 at 05:08:10PM -0500, Brian Ford wrote:
>On Fri, 30 Sep 2005, Brian Ford wrote:
>> 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.
>
>Here ya go.  Self explanatory STC and cygcheck attached.

As you noted, this is not a regression from 1.5.18.  It is not going to
be fixed for 1.5.19.

cgf

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