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:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=SyzAxQ7
	1Ytr5aaqV20m6VWYkmPoZRaDXbOHoldmbk7abtgmWDawhu6oT0ovPhlEgfhziU2B
	USTdAsW4kqJepNPqMs5ED31RqtN+Vwv95I7p6GzDtvBLwfIz5TRqSQi2qTBm0z+z
	VsjvNmL2NIIuKJFDMT1SwYSBedM8PDycf9mc=
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:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; s=default; bh=jcGHfvaWwQLX4
	t1E5B7MlDJmK7Y=; b=l9q1zgFKQn71KrpinMnPCPufgq1EjUO2D2KlhPQxZs5uA
	EZinPCryVl3sgdJj7M8El/gTpMO++knR34Jxy+i6zfpk/4EzXMrpEybMYhLsos9O
	32fMbcnB8hXt1V20Nm9crx6I5SacQicxQcd6yyltFqt2W1zY0utaual6xBVVow=
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=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=scientific, smooth, ear, who's
X-HELO: mail-io1-f52.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;        bh=hYQL4vcfM6KGJ7BzRdyETNZ08sodJBhB3aeF6m9U6DA=;        b=NSREFl8TbZAI7f/DrIcT9o4FiMlKjM1dlFnYpdlRszS+Y26MowHYoYD4SUj01/7pl6         ZOW9mqjFlDahvLMwr+APYS5X0lBXNWbAZvgstdIKxgeD7qwzr+7D5ksMZ/boqOJj6nMT         eOy97N5LYuTcAVUmU0XC9UMdlWn7wD24ahMSuYSwkUG8HiJ8VVCHySwhlJF5D4iSMHqY         YBOSe3kJw87Xp7m0NFY2W8LC7Ah+TGCBPiNy3K0bjf0BjT1aEz/bY/691gAhcG2F5VW6         Bf3RirqsrB7uKkmXMfmdO2aaQbcON5+r3yYyQTvkg7aaXZkwOPbvD8nQJrYQzPfHlZA1         z4/w==
MIME-Version: 1.0
References: <ac18c114-ff4b-0329-7a5d-9dab745cf2ee AT yahoo DOT com> <5c7607bb DOT 1c69fb81 DOT ce2c0 DOT 65ce AT mx DOT google DOT com>
In-Reply-To: <5c7607bb.1c69fb81.ce2c0.65ce@mx.google.com>
From: "E. Madison Bray" <erik DOT m DOT bray AT gmail DOT com>
Date: Wed, 27 Feb 2019 16:51:02 +0100
Message-ID: <CAOTD34YOqRDNJiuD2A93WyT98wVWie=E-+x2Tc+SykSOTAwMzg@mail.gmail.com>
Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes

On Wed, Feb 27, 2019 at 4:45 AM Steven Penny wrote:
>
> On Tue, 26 Feb 2019 19:21:15, "Jerry Baker via cygwin" wrote:
> > Well I guess it's a good thing there's only one possible state of
> > Windows 7 x64 which allows us to determine that there's no possibility
> > of a bug simply by running a single instance in one VM. We're going to
> > turn the world of unit testing on its ear with this information.
>
> correct, multiple states are possible. this is why the scientific method defines
> a control:
>
> https://wikipedia.org/wiki/Scientific_control
>
> in this case that would be a clean virtual machine. if you cant or wont do that,
> then you must understand that you only have yourself to blame.

I understand this thread has been heated, and it hasn't been just you
who's been impatient by any means.  But maybe it will help smooth
things over by avoiding words like "blame" and finger pointing.  If
someone has a broken Cygwin on their system that works on other,
similar systems it's not necessarily the user who's to "tlame".

Yes, PEBKAC is always a possibility, but since you mentioned the
scientific method I'll just add that we have no evidence of that
either.  Windows, much someone's working installation of Windows
(which can have a lot more going on on it than a fresh VM) is an
enormously complex system, and it's entirely possible that Cygwin is
*broken* on that particular configuration through no fault of the
user.

Unfortunately, without concrete steps to reproduce the problem, the
rest of us can only speculate.

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