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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=pl/Ib/hzk0A3hDdO
	fCBYUIEBD8w4kMWQlUMssu6/t55uUMsmwzbB+1KbVw18Rv32gY6TCn6c9yrdN0N7
	gueAXHDNkAPP9e2hUDGAZZKzEfFo2rf+M41B6WWfUx0f93jf0ZpH/M50QIFy1dKz
	iYj3ca7KudcyGbRK2V+DrmhTTvo=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=i40HcuzgGS3T8NQdvQxgab
	MIq3w=; b=EWTKNaS8De+SBeAMZnixOIKk4QMTZPO3gAsSaFSZwTaVT3RuSZCiTw
	QqgwHHCKBaDnw1bh25R+Doa6YZX+r1XhHsAL9PMlWbh+y6kcMpKbwl6aKnSxEAKP
	p1jhwcmUOswxi27J+UpCqoT91nBBP6Tkq7K6AL9rbFee/wC+4YbTQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-3.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=activity, H*MI:sk:fqA1Ptu, H*f:CAD8GWsvx7QM7, settled
X-HELO:	smtp-out-no.shaw.ca
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: Is Cygwin 3.1.X Stable Enough to Use?
To:	cygwin AT cygwin DOT com
References:	<817yBTNxU4176Set DOT 1582206646 AT web03 DOT cms DOT usa DOT net> <1613327751 DOT 20200220213642 AT yandex DOT ru> <CAD8GWsuRiKMsDNFJVAT=48uRA92VbVfxUQxmCm7S-j326it2bQ AT mail DOT gmail DOT com> <20200221092029 DOT da2c51cec466dc8339ee0906 AT nifty DOT ne DOT jp> <CAD8GWsvOjjSx9t6QQu3QpGT5AJ9LoFkGrwMTiwb+1p8Cvkti7Q AT mail DOT gmail DOT com> <20200221110600 DOT adf918ed5dbc4fce5a1067f3 AT nifty DOT ne DOT jp> <CAD8GWst5LGjE3iP8HLnnzARMiqONrUy=Fph95O9gPZTZZVgofQ AT mail DOT gmail DOT com> <CAD8GWsu8+_qatfxMzHm4GZf0mgCfY7zkvPeojgqLFbDytBZNQA AT mail DOT gmail DOT com> <20200221184114 DOT 165a2b601b22bd0a990c9247 AT nifty DOT ne DOT jp> <CACac1F_s4sRTmtTdsjSoHy1mB68=1gWLt0Nw_tVJ4Xs-0UiB8w AT mail DOT gmail DOT com> <CAD8GWsvx7QM7+2FT-+yPMB+XHTt-TEx4pWhDs=fqA1PtuWMaVA AT mail DOT gmail DOT com>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID:	<97d019bd-48b9-4725-6a7f-9b4cec7f73f1@SystematicSw.ab.ca>
Date:	Fri, 21 Feb 2020 14:34:23 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version:	1.0
In-Reply-To:	<CAD8GWsvx7QM7+2FT-+yPMB+XHTt-TEx4pWhDs=fqA1PtuWMaVA@mail.gmail.com>
X-IsSubscribed:	yes

On 2020-02-21 07:26, Lee wrote:
> On 2/21/20, Paul Moore wrote:
>> On Fri, 21 Feb 2020 at 09:41, Takashi Yano wrote:
>>> On Thu, 20 Feb 2020 21:47:25 -0500, Lee wrote:
>>>> On 2/20/20, Lee wrote:
>>>>> I'll try backing out the registry change & see if it still happens.
>>>>
>>>> It doesn't happen now.
>>>>
>>>> I deleted HKEY_CURRENT_USER\Console\VirtualTerminalLevel
>>>> rebooted
>>>> deleted all the .o files under /source/tidy & rebuilt
>>>> The output of cmake looks normal
>>>>
>>>> I updated cygwin this morning:
>>>> 2020/02/20 07:49:28 Augmented Transaction List:
>>>> 2020/02/20 07:49:28    0 install cygwin                 3.1.4-1
>>>> 2020/02/20 07:49:28    1   erase cygwin                 3.1.2-1
>>>> 2020/02/20 07:49:28    2 install cygwin-devel           3.1.4-1
>>>> 2020/02/20 07:49:28    3   erase cygwin-devel           3.1.2-1
>>>>
>>>> is it possible that fixed it?
>>>
>>> I am not sure. In my environment the problem does not occur
>>> even with cygwin 3.1.2. Therefore, the cause cannot be identified.

>> I had the same issue and it was fixed by 3.1.4, so yes upgrading was
>> likely the fix.

> So, getting back to the OPs question about the stability of the
> current cygwin.. I'd say yes, it is "stable" now.  The only problem
> I've seen doesn't happen after I upgraded and other pty issues seem to
> be closing fast

Check the git logs linked from the https://cygwin.com/snapshots/ page:

	https://sourceware.org/git/?p=newlib-cygwin.git;a=shortlog
	https://sourceware.org/git/?p=newlib-cygwin.git;a=log

and the patches mailing list archive:

	https://cygwin.com/ml/cygwin-patches/current/threads.html

and you will see there is current activity which may be settled by the next
release 3.1.5.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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 -