From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64006 invoked by alias); 26 Oct 2017 15:48:42 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 63989 invoked by uid 89); 26 Oct 2017 15:48:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.8 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=4.6.2-1, behavour, Fixes, windowlist X-HELO: blaine.gmane.org Received: from Unknown (HELO blaine.gmane.org) (195.159.176.226) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 26 Oct 2017 15:48:40 +0000 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1e7kON-0005AC-4f for cygwin@cygwin.com; Thu, 26 Oct 2017 17:48:23 +0200 To: cygwin@cygwin.com From: Andrew Schulman Subject: Re: [ANNOUNCEMENT] screen 4.6.2-1 Date: Thu, 26 Oct 2017 15:48:00 -0000 Message-ID: References: <717888519.20171025131833@yandex.ru> <738560212.20171026181127@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes X-SW-Source: 2017-10/txt/msg00334.txt.bz2 > Greetings, Andrew Schulman! > > >> > screen 4.6.2-1 is now available in Cygwin. This is an upstream bug fix release. > >> > The release announcement says the release includes: > >> > >> > * Fixes: > >> > - revert changes to cursor position restore behavour (bug #51832) > >> > - set freed pointer to NULL (bug #52133) > >> > - documentation fixes > >> > - fix windowlist crashes (bug #43054 & #51500) > >> > >> > See the git log http://git.savannah.gnu.org/cgit/screen.git/log/?h=v.4.6.2 for a > >> > full list. > >> > >> Still hangs http://sourceware.org/ml/cygwin/2017-05/msg00448.html mid:16810313565.20170527142723@yandex.ru > > > OK. I know the problem is still there - I haven't forgotten. But I don't > > have any ideas yet about why. > > Sorry if that felt bothering, I didn't mean that. Not at all, no bother. It's appropriate to remind maintainers sometimes of problems that haven't been solved. > > Dan's reply to your message[1] has a start on debugging the problem. > > > Andrew > > > [1] https://sourceware.org/ml/cygwin/2017-05/msg00450.html > > I apparently missed this message. > As I'm not into C programming myself, I'll patiently await somebody with skill > and knowledge to attend to the issue. I'm a little better off, but it would take me a while to work through the debugging. I'd also be happy if someone else figured it out. Andrew -- 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