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,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <f5b62w8yvc2.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>
Date: Mon, 8 Nov 2010 12:36:29 +0000
Message-ID: <AANLkTi=TE=T6ESQvkZOQRC8ue2cH9ZU7PbJaC5fpJD-m@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
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 8 November 2010 10:15, Henry S. Thompson wrote:
> Bear with me please, this is moderately complex:
>
> I run mintty out of the Quick Launch bar as follows:
>
> =C2=A0C:\Cygwin\bin\mintty.exe =C2=A0/usr/bin/screen -q
>
> and in one of the resulting tabs read mail using gnus in xemacs on a
> Debian box remotely via ssh. =C2=A0About once a week as that remote gnus =
is
> painting the subject lines in my spam box, the whole thing freezes
> solid.
>
> screen doesn't respond to escape commands, ~. does nothing, Control-C
> has no effect, trying to close the window results in the "process not
> responding" popup.
>
> It's not repeatable, in that reconnecting and changing to the same
> gnus Subject buffer will succeed.
>
> I _presume_ some obscure character code is responsible. . .
>
> Two questions:
>
> =C2=A01) Anyone else seen anything like this?

Not as such, but it could be to do with the following issue: if you
cat a big file and press any key that sends a character, the terminal
and cat will be deadlocked, like so:

$ ps
O    2408       1    2408       2408    ? 99498 12:27:13 /usr/bin/mintty
O    2672    2772    2672       1580    5 99498 12:27:19 /usr/bin/cat

They're both in write(), waiting for each other to read data from
their side of the pty. Happens with all the pty-based terminals.
Killing the cat resolves the deadlock, and the terminal merrily
continues.

> =C2=A02) Any easy way to provide useful details? =C2=A0I would be happy t=
o run a
> =C2=A0 =C2=A0debugging build if supplied, but really can't run for days u=
nder
> =C2=A0 =C2=A0strace. . .

So the first thing to check is what state the mintty and screen
processes are in when this happens, using 'ps', and to try killing
first screen and then mintty from the command line.

You could also try hammering the keyboard during the screen updates in
question to see whether you can force the issue.

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