X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RP_MATCHES_RCVD,TW_CG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
Message-ID:	<32629312.post@talk.nabble.com>
Date:	Tue, 11 Oct 2011 03:24:22 -0700 (PDT)
From:	"jan.kolar" <kolar AT math DOT cas DOT cz>
To:	cygwin AT cygwin DOT com
Subject:	Re: Problem redirecting stderr to pipe in subprocess
In-Reply-To:	<20111011034441.GA20346@ednor.casa.cgf.cx>
MIME-Version:	1.0
References:	<4E906DD1 DOT 50107 AT cornell DOT edu> <4E90C308 DOT 9090508 AT cornell DOT edu> <20111009235815 DOT GA18203 AT ednor DOT casa DOT cgf DOT cx> <20111010220608 DOT GA1568 AT ednor DOT casa DOT cgf DOT cx> <4E93AD5E DOT 6060001 AT cornell DOT edu> <20111011034441 DOT GA20346 AT ednor DOT casa DOT cgf DOT cx>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

Christopher Faylor-8 wrote:
> 
> On Mon, Oct 10, 2011 at 10:43:42PM -0400, Ken Brown wrote:
>>My STCs still don't work right for me under the 2011-10-10 snapshot. 
>>The bash subprocess no longer shows as stopped when I run ps, but it 
>>doesn't produce any output either, and it doesn't terminate for several 
>>minutes.  I eventually get the following message on the terminal
>>
>>       1 [main] bash 7604 sig_send: wait for sig_complete event failed, 
>>signal -39, rc 258, Win32 error 0
>>
>>and bash leaves a stackdump.  Are you seeing something different?
> 
> For me it works on Cygwin the same as it does on Linux.  No hang,
> obviously.  If it worked like the above I wouldn't have announced
> a fix.
> 
> cgf
> 
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> 
> 
> 

Then I'll put more words what I meant saying "External conditions might play
its role."

For example, a problem might appear to be fixed when cygwin1.dll restarted,
also depending
on whether and how rebase/rebaseall was applied.
This is particularly true for well-known (among developers) fork-related
problems.
This however might not(?) be fork-related.

I think there is a single occasion when __SIGFLUSHFAST (-39) is sent -- in
__main.
Is it right after inicialisations ? (When exactly? -- I do not understand).
Certainly it is before bash -ci ls  opens /dev/tty.

JK


JK
-- 
View this message in context: http://old.nabble.com/Problem-redirecting-stderr-to-pipe-in-subprocess-tp32616089p32629312.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -