X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=bMoWuiIv6unlNc/0fUqOF0srMfEqEHKUBbF5azsHAqwyLvYM2LUi6 zMtimd7aPqSLRD7zFYAaHKlPLlrHztihNV8LKDEUy4eL276eLq+GU/QzvL7ww90M cRScxPqiIAmebk9r1Y/+EY1PySFLCsGX/7Xi/1OgcmW5F9BT/F26HQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=pPe1OgrqK/PkDypxclvwX0JQA7s=; b=Uq6sF2jSdnbOppXlmCZdklsY9FhP FS0NDtTRG06Tf22c5k0BIE0a/M2SehZNOFVXGsKI6V6OUlBZRHXdy0nBr+8Djg86 DziwzDDhMV6LWw0UZe0P+3fQl8E5LKQ9TsBa3DrdbbxPA1i3uQK6yaR6qeQ0vMnr FZmH4fmK0FVZA6o= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,TW_RX autolearn=ham version=3.3.1 To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: pty issue causes 'screen' to hang when run from mintty as detached Date: Mon, 17 Jun 2013 11:27:03 -0400 Lines: 30 Message-ID: References: <51B63D88 DOT 6000508 AT codespunk DOT com> <20130617135835 DOT GA852 AT ednor DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt > On Mon, Jun 17, 2013 at 06:08:27AM -0400, Andrew Schulman wrote: > >> > Do we have any idea whether the problem is with mintty or with screen? > >> > >> I observed the same behaviour as the OP, but also reproduced it in > >> rxvt and xterm, so not a mintty issue. Since it works in a console, > >> the Cygwin pty layer has to be the main suspect, unless screen has > >> specfic code for Cygwin consoles or ptys? > > > >I don't think so, but there's one big, crufty old patch that I had to use to get > >screen to run a few years ago. > > > >The version of screen that we're using now in Cygwin, 4.0.3, is about 8 years > >old. There haven't been any official new releases since then, but development > >has continued and there have been a lot of improvements. I'm in the process of > >building an updated package from the latest git, and that version appears not to > >need any of the patches I used to have to use to get screen to compile and run > >in Cygwin. > > > >So, I suggest that we wait until the new screen test release comes out, within a > >few days, and see if that fixes the problem. > > I looked at this briefly over the weekend and saw a problem in Cygwin's > pty handling code. I don't know exactly what the problem is yet but there > is something not quite right there. Something is closing a windows handle > and that's causing a SIGHUP to be sent to the pty owner. That's not right. > > I'll fix this problem eventually but it will be interesting to see if a > newer screen behaves any better. No, I just tested it on the latest screen release, and the problem still occurs. -- 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