X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_63,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20090903002631.GA4530@ednor.casa.cgf.cx>
References: <slrnh9pnbv DOT ljh DOT tuomov AT beer DOT modeemi DOT cs DOT tut DOT fi> 	 <slrnh9pthu DOT 2k8 DOT tuomov AT beer DOT modeemi DOT cs DOT tut DOT fi> 	 <h7ja53$cos$1 AT ger DOT gmane DOT org> 	 <20090901141602 DOT GD16845 AT ednor DOT casa DOT cgf DOT cx> 	 <4A9D556C DOT 8070808 AT gmail DOT com> 	 <f60fe000909011105s6aa1d2bejbcf1735e32cc8cbf AT mail DOT gmail DOT com> 	 <h7kp2k$nf9$1 AT ger DOT gmane DOT org> 	 <5a05e0e60909020719i46ab067y6a78dc5e4b6da366 AT mail DOT gmail DOT com> 	 <agkt95ta81mdbr1fm3a3m5imq06qaa0b5v AT 4ax DOT com> 	 <20090903002631 DOT GA4530 AT ednor DOT casa DOT cgf DOT cx>
Date: Thu, 3 Sep 2009 00:59:50 -0400
Message-ID: <5a05e0e60909022159m2e3c29acs673edd314f759b52@mail.gmail.com>
Subject: Re: GNU screen hangs
From: Dave Steenburgh <dave DOT steenburgh AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
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 Wed, Sep 2, 2009 at 8:26 PM, Christopher Faylor wrote:
> On Wed, Sep 02, 2009 at 04:14:11PM -0400, Andrew Schulman wrote:
>>screen is difficult to debug, because it uses two communicating
>>processes, one in the foreground to talk to your terminal, and one in
>>the background to talk to the processes in each window.
>
> That's not that hard to debug. =A0You just attach two different copies of
> gdb to each process after screen starts running.

...but you still need to know what you're looking at, and what to look
for.  It also helps to be well-versed with gdb, and I am not.

There was another hanging today, but this time I paid a little more
attention, and I think bash was the problem, not screen.  I never got
a prompt in that window, but I could create another window and I did
get a prompt there.  If that's what's been going on, I'm not terribly
concerned about it.  However, it would be nice to figure out what and
why and how to fix it.


On Wed, Sep 2, 2009 at 4:14 PM, Andrew Schulman wrote:
> ...if you're using a DOS terminal, you need to set CYGWIN=3Dtty in the
> environment before you start your terminal...

Fortunately, I figured that out at some point.  However, I haven't
bothered to look into what that really does, so it seems like voodoo
to me.


On Wed, Sep 2, 2009 at various times, various people wrote:
> mintty, rxvt, puttycyg, poderosa, console2

Thank you all for the suggestions.  (Did I miss any?)  Hopefully I
will find one of them agreeable.

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