X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 29 Sep 2010 11:20:27 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: gitk kills bash shell
Message-ID: <20100929152022.GC11507@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4CA23B9F DOT 20506 AT ece DOT cmu DOT edu> <AANLkTinvLdtnMoMWGPBKQyXgtK+tNQqckBtRM-1Z8Szd AT mail DOT gmail DOT com> <4CA314E3 DOT 4020808 AT ece DOT cmu DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4CA314E3.4020808@ece.cmu.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On Wed, Sep 29, 2010 at 12:28:51PM +0200, Ryan Johnson wrote:
>  On 9/28/2010 9:40 PM, Jeremy Ramer wrote:
>> On Tue, Sep 28, 2010 at 1:01 PM, Ryan Johnson<ryanjohn AT ece DOT cmu DOT edu>  wrote:
>>> This sounds suspiciously similar to a problem that hit me a while back:
>>> http://www.cygwin.com/ml/cygwin/2010-09/msg00225.html
>>>
>>> The short version is, running certain apps in the background triggers a bug
>>> in tty handling.
>>> Last I heard Corinna was having trouble diagnosing because the bug also
>>> kills strace :)
>>>
>>> No fix yet AFAIK.
>> I was afraid of that. It just started happening for me after upgrading
>> to cygwin 1.7, as well as to others in my company.
>One nice thing, at least, is it takes a very specific setup to trigger 
>the bug. You may be able to get a usable workaround by changing how it's 
>called (see the thread above for ideas).
>
>Hopefully we get a fix for this soon, though.

http://cygwin.com/ml/cygwin/2010-09/msg00852.html

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