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=cY7KFHdXs28U0XCeyA3p4MtII/opikwS88el+SrRr2p9zAGkrVhHF
	tz8cwttKsSw0re4WjemSMFRmHwJjD3CCQJOxksp10LWhKT6ymULrq9wyuVU/cCf8
	7UCXvlsroiJOADyEKwTKmCveivQWHZxF6SFo6IDZtNvwHnOM0EJGzE=
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=4hva8FFwfwARORsD+NNE1lrlFPU=; b=bslcf9vIyMG1w5QOHAWH+zsC3dQH
	GE6fB9lZ3OScupLUfWv5YEwVnhbY86pdR6hzXJ7e3QJrgrtD3Cv9MDwBhDJrB28q
	7WJeMT7q8kOoQI5INQxgcOxx98YtpxyJFsrhkxa34F39vWfrLojUi9ivE4PbnpRJ
	36N/I3aJUZNORKQ=
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=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham 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: U2FsdGVkX1/f2MBV+SkKMtxyNtIiPI0C
Date: Thu, 23 May 2013 11:03:19 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: CppUTest generated executables hangs after cygwin auto-update
Message-ID: <20130523150319.GB7647@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <519E0450 DOT 60704 AT trackitsystems DOT de> <20130523122928 DOT GA23537 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130523122928.GA23537@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, May 23, 2013 at 02:29:28PM +0200, Corinna Vinschen wrote:
>On May 23 13:58, Ralf Glaser, track IT wrote:
>> Corinna,
>> 
>> when i replace the original cygwin DLL (which was installed with
>> cygwin-1.7.17) with the snapshot from 2012-11-23 the problem is
>> already there.
>> Maybe just replacing the DLL is not what you had in mind?
>
>That was all, yes.  Did you test the 2012-10-16 DLL, too, by any chance?

As long as we're testing snapshots, how about testing the latest one?

cgf

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