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=IVjmZPJyAFwCvlpXgyjvcm5AExp5rdeXq7GYW9YbEnfJqbcT1jnS1 tAvI4cCQd29HVD31IleDgCtnltA1Iui89Nk3fU0GSipAATBaNakxEfPxAZ03Fc4S aaaK+SmbcfiJ/6YgtBuDzdR9cAhJ0wnaHzx6K1NZ0r+r656E2hoUDo= 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=9uKtWJDQtnPTgsYoPNPwoRaxtEw=; b=GvMsvXXzwQthJz83vT1/O7/oUfMJ 73Bv3DWNEfdtECoezK9In1Bho+4w2JhmWltGvERcn1JV8nPkM2OeI0wjqra7H63z 6G2mA3zK14Z4F1pJ1ox5lQIwZRKO+lsfGw/sEpNfUpnXyi02ikPggAP8o0Ts0LXi CrNdJDKs3lw/cak= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.5 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.3.1 Date: Thu, 23 May 2013 11:34:06 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: CppUTest generated executables hangs after cygwin auto-update Message-ID: <20130523093406.GG22259@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <519DDD82 DOT 7070109 AT trackitsystems DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <519DDD82.7070109@trackitsystems.de> User-Agent: Mutt/1.5.21 (2010-09-15) On May 23 11:12, Ralf Glaser, track IT wrote: > Since last cygwin update executables generated by the unit testing > framework CppUTest hang on execution. Same behaviour for CppUTest > V2.3 and V3.4. > > Downgrading base->cygwin from 1.18.1 to 1.17.1 fixes the problem. Any chance you could try to find out which of the Cygwin DLL snapshots from http://cygwin.com/snapshots/ introduced the problem? This must occur somewhere between the 2012-11-23 and the 2013-04-09 snapshots. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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