Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Date:	Sun, 18 Aug 2002 00:15:57 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: Another problem with MC + subshell on cygwin
Message-ID:	<20020818041557.GA9982@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<57228872451 DOT 20020818020843 AT gmx DOT net> <20020818015104 DOT GC15437 AT redhat DOT com>
Mime-Version:	1.0
In-Reply-To:	<20020818015104.GC15437@redhat.com>
User-Agent:	Mutt/1.3.23.1i

On Sat, Aug 17, 2002 at 09:51:04PM -0400, Christopher Faylor wrote:
>Probably the right way to fix this is for the parent process not to
>deliver the SIGCHLD to itself until the child has actually been suspended.
>I don't know of any way of figuring out if the child is really suspended
>though.

I tried to fix this by not using SuspendThread at all.  Instead, there
is YA event (called sigCONT) which the process waits on.  Essentially we
were trying to synchronize using SuspendThread/ResumeThread and
Microsoft tells you that you shouldn't do that...  It shure would be
convenient if it was possible, though.  It would mean one less handle.

Oh well.

Anyway, I've checked in a change and am generating a new snapshot.

cgf

- Raw text -