X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 12 Jul 2012 18:14:21 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: perl-5.14.2 switch
Message-ID: <20120712161421.GC3406@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAHiT=DEgVMRvLZ2J64FEdhXRBe6VYR0fypsWpk8_aj0bHYsWGQ AT mail DOT gmail DOT com> <CAGvSfex6-P9PB6UJ56EPRMCjQUqKmgv=NygwXy1Jzq0r3C-o=g AT mail DOT gmail DOT com> <CAHiT=DHsH_sZ9MPyc7o=t2m_Xb_XnD6KLXeMZ686oa3_-yYQCw AT mail DOT gmail DOT com> <C969B6CE944F4D9CBEE35FC1BFBFE14E AT multiplay DOT co DOT uk> <87mx36z0yo DOT fsf AT Rainer DOT invalid> <7FA8477365204CA6B4617E7279967C24 AT multiplay DOT co DOT uk> <87a9z6ywvp DOT fsf AT Rainer DOT invalid> <60B4845A414A4F228982AB4DEAF4D4FE AT multiplay DOT co DOT uk> <87pq81d09k DOT fsf AT Rainer DOT invalid> <CAHiT=DHYGL6ycTxMtKdWZUJ5tL_unQBNWognZ7HAVu6eTK21_w AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAHiT=DHYGL6ycTxMtKdWZUJ5tL_unQBNWognZ7HAVu6eTK21_w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Jul 12 10:24, Reini Urban wrote:
> Well, I'm not so happy with threads. They seem to be more broken than with 5.10.
> But I like 5.14.2 generally at most of all also, much better than the
> completely flawed 5.16.

Is this thread problem something Cygwin-specific, a Cygwin bug perhaps?
If so, can you nail that down into a simple C testcase?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          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