DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Hwqz+uJWlGyVWEBn
	Gx07nDsQ8RtdQQN8Aps1ZJa0G2UxONVjLn2Hv2O9MNmlVi9vUGH0d2XxxkXwwniZ
	H9rrnm9I+a5HR12Y4d9WBlDDGRf929FImUVQQb3vdP22iOKur6XHmH2kdlgUxWjv
	uVuVnJJjhRqtORFEwfjyG9qwndI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
To: cygwin@cygwin.com
References: <9e344bdc-758b-5711-b25a-1ed2e46952be@yahoo.com> <746a01c6-0faf-aff3-51e6-c0e129a56cc4@yahoo.com> <110b2dfb62fa274469d2d2fae586fb99@smtp-cloud7.xs4all.net> <f3833886-dd90-b445-8ba5-e3e3407d28ee@yahoo.com> <66C04238-FC33-4926-952D-775BF5DEBE2C@solidrocksystems.com> <b34bc30d-9fd3-bab8-b41d-1b5f2c2f7ac4@yahoo.com> <c985aa40-3f68-9385-3d8e-16bf6a69f763@cornell.edu> <f9b58252-a834-94a8-d700-ccfae9a2900b@yahoo.com> <06d6e35d-b645-61c2-089b-8256194168ef@yahoo.com> <CAJ1FpuNbULAo1Gb5Fo7w30PbxdZ9W=XFpiXAADCPqrhrM-TbEg@mail.gmail.com> <c627ae61-2b16-8c01-d0fe-31d48aae8821@yahoo.com> <CAJ1FpuO1nVEySyK1rc7c4AGx4+GsAHikBb54akebky8-yXM1HQ@mail.gmail.com> <35062835-c3cd-799e-d13a-16f954db2a19@yahoo.com> <02f492d9-b334-1dab-aedb-17a747ede36b@SystematicSw.ab.ca> <6b67157a-a9c8-1a72-8997-be9ea8a00a14@yahoo.com>
From: Eric Blake <eblake@redhat.com>
Message-ID: <a031c023-b8fe-cf63-ac12-1c543ee4135a@redhat.com>
Date: Wed, 27 Feb 2019 14:27:24 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <6b67157a-a9c8-1a72-8997-be9ea8a00a14@yahoo.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 2/27/19 2:19 PM, Jerry Baker via cygwin wrote:
> On 2/26/2019 10:55 PM, Brian Inglis wrote:
>> As Cygwin is a rolling release system, if you are not running current
>> releases,
>> some CVE security issues may remain unpatched, and your system may not be
>> compliant to your corporate security policies (you may want to check
>> with your
>> IT security and/or IT auditors).
> 
> I narrowed it down to my network. If I unplug the Ethernet cable the
> problem disappears. If I plug it in, the problem returns. I can
> reproduce it 100% for an hour straight, going back and forth.

Off-hand, I would suspect that the newer Cygwin has code that tries to
access a network resource (perhaps because you have a "//name" in your
$PATH, or perhaps because of local vs. network username), and that the
process hangs waiting for the resource to time out when you have the
cable plugged in (or even has a bug that causes an inf-loop), but
quickly falls back to something that works when the network is not
present. Corinna will have more ideas about how to test which particular
network call is hanging, as well as being more familiar with recent
changes in network username validation, for ideas on better debugging this.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org

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