X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com 02D33TeV007792
X-Nifty-SrcIP:	[125.0.205.54]
Date:	Fri, 13 Mar 2020 12:03:39 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: gnu screen crashes on ssh disconnect
Message-Id:	<20200313120339.78764c4c49d129b0d3d60942@nifty.ne.jp>
In-Reply-To:	<CAHSx_Ss7rf1LMBh8CeyNzMHKO2uXxLWGYxJ0oh5wKOktZidW9g@mail.gmail.com>
References:	<CAHSx_Ss7rf1LMBh8CeyNzMHKO2uXxLWGYxJ0oh5wKOktZidW9g AT mail DOT gmail DOT com>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-2.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,
	SPF_PASS autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	Cygwin mailing list <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<http://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On Thu, 12 Mar 2020 19:01:41 -0700
Wayne Davison wrote:
> In recent Cygwin versions I've had gnu screen crash if the parent ssh
> connection closes before an explicit disconnect is performed. If an
> orderly screen disconnect happens first, future closed connections
> (after reconnecting to the screen session) no longer crash screen.
> 
> To reproduce:
> 
> I ssh into my Windows 10 host, move my .screenrc file out of the way
> (to keep the config the default) and run "screen" to start up a basic
> screen session. I then use the ssh close-connection key sequence
> (Enter, tilde, period) to close the connection. When I log back in,
> the ps command shows that screen is already dead and "screen -ls"
> shows a dead screen to clean up using "screen -wipe". If I start a
> fresh screen and use screen's Ctrl+A d key sequence to detach, I can
> use "screen -r" to reconnect and from this point on a lost connection
> no longer makes screen crash, even on future reconnects.
> 
> I haven't seen this crash on Ubuntu, but since it isn't on the same
> version, I tried compiling 4.8.0 to see if that might make it crash --
> it did not. I then compiled the source on Cygwin (without any
> configure options) and that version has the bug, so I guess that this
> is either a Cygwin issue or something weird in my Windows setup.
> 
> Is anyone else seeing this crash?
> 
> I'm attaching a cygcheck.out file that has a couple secrets elided.
> I'll note that I just started to run with disable_pcon set, but it's
> been crashing with and without that.

Thanks for the report. This seems to be a problem related to pseudo
console. I will submit a patch for this issue shortly.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
--
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

- Raw text -