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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=g1fAKUTed4RHldarNmyElPXpppsXmv70y1ltvKLgOqKA0OfT3EYt1
	p6eY6KDvD0gzveVMCfNf1Gt/hImMzPd29cQ0k5F3DQcp5VmYJa04ujz/NDDu5AZd
	sYQoSqTtsvkEJ4MFQyB5JpMlZdKCnFfRNaiPNgpuHfgI3ujFho4QOc=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=KVu3vE8rpSGWw/+gmC4+gvnWyf8=; b=KED5rkCBqmKtidxeTGik8ZjB4Fgc
	R66TzFXLFx1I2YUBLRxsy+m7cho6wx2Y6KdNx4VfHAOI51+hby7tTuJ1LAN/lbs9
	LYorXE7lPBmNVYtkbt1Z80VqSDbMke8nouFmDyCof8JhADwUEcq5vXP314CbIB4x
	Konf1oH+6WbxM6k=
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
X-Spam-SWARE-Status:	No, score=0.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RDNS_NONE autolearn=no version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18JfpYvHKgJEqzjPSVKtCUU
Date:	Wed, 31 Jul 2013 13:21:47 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: possible bug in 1.7.22-1 core DLLs
Message-ID:	<20130731172147.GA1692@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<6 DOT 2 DOT 5 DOT 6 DOT 2 DOT 20130731121524 DOT 03acf020 AT binnacle DOT cx>
MIME-Version:	1.0
In-Reply-To:	<6.2.5.6.2.20130731121524.03acf020@binnacle.cx>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Wed, Jul 31, 2013 at 12:24:32PM -0400, starlight DOT 2013z3 AT binnacle DOT cx wrote:
>Have been running 1.7.16 for some time and living with the annoying
>CTRL-C hang bug.
>
>Tried swapping in cygwin1.dll cyglsa.dll and cyglsa64.dll from 1.7.22-1
>without (thankfully) updating the entire CYGWIN release.
>
>The 22-1 DLLs fix the CTRL-C problem, but cause a high-intensity
>parallel build job to fail consistently.  Looks like 'imake' output
>Makefiles are somehow getting corrupted.  The build runs entirely over
>a CIFS share via Samba 3.6.10.
>
>I suppose that some dependency conflict between older version DLLs and
>the newer core DLLs could be the cause, but one would hope that the
>APIs would be relatively stable at this point.
>
>Of course I put everything back, but am reporting to the list since
>this would qualify as a serious regression.
>
>To some extent I'm willing to attempt to hunt down what's failing, but
>I have limited time to do so.

You are right in assuming that newer DLLs should work with older
binaries but no one is willing to do tech support or debugging based on
vague problem reports.  So, it isn't clear exactly what you're
expecting.  If you think someone is going to take a "1.7.16"
installation and then drop a newer cygwin1.dll into it to debug your
problem then you are likely going to be disappointed - especially if you
can't even be bothered to subscribe to the mailing list.

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