Date: Tue, 11 Oct 2011 08:18:27 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem redirecting stderr to pipe in subprocess
Message-ID: <20111011121827.GA30683@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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> <32629312 DOT post AT talk DOT nabble DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <32629312.post@talk.nabble.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Oct 11, 2011 at 03:24:22AM -0700, jan.kolar wrote:
>
>
>
>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.
>
>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.

You're speculating.  Speculation is not necessary.  This condition is
debuggable and it has nothing to do with anything you've proposed so
far.

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