X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.0 required=5.0	tests=AWL,BAYES_05,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_SV,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <f5btyj359ec.fsf@calexico.inf.ed.ac.uk>
References: <announce.AANLkTinNr93j+S44rcV6KiZU7-mMR8XGe+VOcG_AHdE7 AT mail DOT gmail DOT com>	<f5b62w8yvc2 DOT fsf AT calexico DOT inf DOT ed DOT ac DOT uk>	<AANLkTi=TE=T6ESQvkZOQRC8ue2cH9ZU7PbJaC5fpJD-m AT mail DOT gmail DOT com>	<f5bd3q6opd7 DOT fsf AT calexico DOT inf DOT ed DOT ac DOT uk>	<AANLkTikjGHcKRgVBaDcta=yry9YeK=qL2i1fi7P-ZXvG AT mail DOT gmail DOT com>	<f5btyj359ec DOT fsf AT calexico DOT inf DOT ed DOT ac DOT uk>
Date: Sun, 28 Nov 2010 09:59:29 +0000
Message-ID: <AANLkTinpRRJZssaJ8GpPLJU=MxufKh1zPJ4evOXXe_F=@mail.gmail.com>
Subject: Re: How to debug mintty or screen freeze
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Cc: "Henry S. Thompson" <ht AT inf DOT ed DOT ac DOT uk>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
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 27 November 2010 10:49, Henry S. Thompson wrote:
> Andy Koppe writes:
>>> [screen + mintty freezing]
>
>> Another thing you could try is to enable logging to a file using the
>> --log command option. Perhaps that will show what control sequence
>> triggers the problem. Obviously you'll want to remove any private
>> details before sending the log.
>
> Attached please find the last 50 lines of three occasions of freezing.
> Nothing private therein, so these are complete.

Thank you! I managed to reproduce a crash by catting those three file
in an endless loop. It should now be fixed on svn trunk. Can you give
that a go?

http://mintty.googlecode.com/files/mintty-svn-trunk-r1078-cygwin17.zip

> The problem must be
> timing related and/or some kind of race, as you previously suggested,
> because after the freeze, when I reconnect to the remote xemacs, the
> page that froze half-way through paints just fine. . .

Actually it turned out to be a memory corruption problem due to not
clearing combining characters correctly when scrolling.

> [I don't understand why my previous message lost its substance, and
> consistend only of the attachment -- in any case, here is the text
> that I thought I included in it???]

It showed up ok here.

Andy

--
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