DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=BXv3yOsZVtZimrJcAWg79FWAhD7zSkU5GLXjbajB1KDR0lqRJf6PY
	+49gdDj/L6Ma4KTqbsC6RKCjxbRHqax7RoTJxR9K6meVFHyZVOp3FOwtSGwbLDTb
	Zw3veSeJkEPTGvIMrAq9egKR24YUhKgSQ3IFzw8VsZPqUwfSRgvxvg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 17 Jun 2013 09:58:35 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: pty issue causes 'screen' to hang when run from mintty as detached
Message-ID: <20130617135835.GA852@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <51B63D88 DOT 6000508 AT codespunk DOT com> <phscr81sr0kr02qenquh1s0na4n062u3so AT 4ax DOT com> <CAHWeT-Y0DE4sANnm9yFDooFOmD8VHqLk4jMDe2SOFkBFo5wGog AT mail DOT gmail DOT com> <uhntr81q9q7rr07f131rrkhij32amghs5l AT 4ax DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <uhntr81q9q7rr07f131rrkhij32amghs5l@4ax.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

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.

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