X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
Subject:	Re: How to debug mintty or screen freeze
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>
From:	ht AT inf DOT ed DOT ac DOT uk (Henry S. Thompson)
Date:	Sat, 27 Nov 2010 10:55:33 +0000
In-Reply-To:	<f5btyj359ec.fsf@calexico.inf.ed.ac.uk> (Henry S. Thompson's message of "Sat, 27 Nov 2010 10:49:15 +0000")
Message-ID:	<f5blj4f593u.fsf@calexico.inf.ed.ac.uk>
User-Agent:	Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.21 (linux)
MIME-Version:	1.0
X-Edinburgh-Scanned:	at treacle.ucs.ed.ac.uk with MIMEDefang 2.60, Sophie, Sophos Anti-Virus, Clam AntiVirus
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

[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???]

Andy Koppe writes:

> On 15 November 2010 10:25, Henry S. Thompson wrote:

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

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht AT inf DOT ed DOT ac DOT uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

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