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:	Sat, 17 Aug 2002 21:51:04 -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:	<20020818015104.GC15437@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>
Mime-Version:	1.0
In-Reply-To:	<57228872451.20020818020843@gmx.net>
User-Agent:	Mutt/1.3.23.1i

On Sun, Aug 18, 2002 at 02:08:43AM +0200, Pavel Tsekov wrote:
>>>>>> Strange !!! We'are missing a sigproc_printf output here (sigproc.cc, 675)
>>>>>> Oh, well... it's not so important though :))

You really can't rely on line numbers when you are referring to things like this.
I don't have a sigproc_printf in my version of sigproc.cc at line 675.

>I think a quick and dirty workaround for MC is to put some kind of
>timeout before sending SIGCONT and hope for the best. The best
>solution will be to fix this on Cygwin of course :) I haven't thinked
>of any solution since I've just found it and I'm going to bed since
>it's 2 AM here :)

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.

Upping the thread priority in sig_handle_tty_stop would make the race
less likely, too.

cgf

- Raw text -