X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 3 Sep 2009 09:47:30 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: GNU screen hangs
Message-ID: <20090903134730.GA24917@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <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>  <5a05e0e60909022159m2e3c29acs673edd314f759b52 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5a05e0e60909022159m2e3c29acs673edd314f759b52@mail.gmail.com>
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 Thu, Sep 03, 2009 at 12:59:50AM -0400, Dave Steenburgh wrote:
>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. ?You 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.

I was actually talking to Andrew Schulman, the screen maintainer.

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