X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 2 Sep 2009 20:26:32 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: GNU screen hangs Message-ID: <20090903002631.GA4530@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4A9CF7A1 DOT 8060704 AT googlemail DOT com> <20090901141602 DOT GD16845 AT ednor DOT casa DOT cgf DOT cx> <4A9D556C DOT 8070808 AT gmail DOT com> <5a05e0e60909020719i46ab067y6a78dc5e4b6da366 AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 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. 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