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: Thu, 7 Oct 2004 12:50:21 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Calls to system() blocks return of SIGCHLD signal
Message-ID: <20041007165021.GB14536@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <BADF6263E3618145A44CC3A28C8E1243041461 AT hydra DOT montreal DOT ad-opt DOT com> <20041006184701 DOT GQ29973 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT CYG DOT 4 DOT 58 DOT 0410071118130 DOT 5620 AT fordpc DOT vss DOT fsi DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.CYG.4.58.0410071118130.5620@fordpc.vss.fsi.com>
User-Agent: Mutt/1.4.1i

On Thu, Oct 07, 2004 at 11:30:42AM -0500, Brian Ford wrote:
>On Wed, 6 Oct 2004, Christopher Faylor wrote:
>
>> On Wed, Oct 06, 2004 at 12:24:48PM -0400, Remy Gauthier wrote:
>> >We have noticed (on V1.5.10-1 and V1.5.11-1) that after a call to
>> >system(), the handlers were not being called after the child process
>> >stopped.  This program has this behaviour (removing the call to
>> >system() will restore correct SIGCHLD handling):
>[snip; from Linux system(3)]
>> During execution of the command, SIGCHLD will be blocked, and SIGINT and
>> SIGQUIT will be ignored.
>
>Um..., I think you missed the point here cgf as this didn't answer the
>question.  The key word above is "During".  He was reporting that it
>was still in effect "after", and he identified the cause here:

Shame on me for not reading the original message more thoroughly and
ass*u*me ing that it was a standard complaint about documented system()
behavior.

The fix is trivial and checked in.  I apologize for my incorrect answer
and for any confusion I caused.

This will be in the next snapshot, which I've just kicked off now:

http://cygwin.com/snapshots/

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/