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:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Wc2dZuHg1x9Qub23
	JTClOAs+vN9pKoRzflXTu2xkySCEX9iG8divrPiqq/5HJuQ0oc9HAJcobu7fvfDP
	HNawu81TiZpIaS/6QzDZziIxr2kV+3r16pf2KOCIwHQsRdwD+yUSsfULllHwTNh7
	e1rAcwtePq8Eq5R3GM/rGl5Wdf0=
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:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; s=default; bh=Cru54vSs6Z7NV4LRmRkW0E
	wVDOk=; b=GdKKrM6+7DzrdLlv+kNuvHFH/HnbyaukQ6arNRVPBJSxGNLjOI/Uvi
	9eDzGj4e2J2APVoUVsrcO/iNX8Vab6PBMwHf8ybQ3TTpvpO3ZGhEBfW14XU0PJVp
	5LL3S68SSQKG96/DjIrYeLj6+ONUaNwnTw0JZuQa0zf9z1yMzEH+4=
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=-2.8 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1
MIME-Version:	1.0
X-Received:	by 10.180.87.162 with SMTP id az2mr19010586wib.10.1369102248636; Mon, 20 May 2013 19:10:48 -0700 (PDT)
In-Reply-To:	<B8D164BED956C5439875951895CB4B22110B04EC@WABOTH9MSGUSR8C.ITServices.sbc.com>
References:	<B8D164BED956C5439875951895CB4B22110B04EC AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com>
Date:	Mon, 20 May 2013 21:10:48 -0500
Message-ID:	<CAHiT=DF6cbpKLqON+OwVz_5m9fkW00mYB759GzDPMQLpJ2LCYA@mail.gmail.com>
Subject:	Re: Were the Perl multithreading problems ever fixed?
From:	Reini Urban <rurban AT x-ray DOT at>
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id r4L2B4xB014851

On Mon, May 20, 2013 at 1:14 PM, KARR, DAVID wrote:
> Last year I had reported some problems with a Perl script that utilizes multithreading.  I believe it was Reini Urban who told me that there were known problems with Perl multithreading and that an ETA for a set of fixes was not known yet.  Does anyone know if those particular Perl multithreading issues have been dealt with in later Cygwin releases?  I'm still on 1.7.17.

These were entirely perl related and not cygwin.
And most of the known problems were fixed with the change from
non-thread safe usemymalloc (perl internal malloc) to the thread-safe
system malloc
with 5.14.2.
There are still minor thread problems within perl, but nothing dramatic.

The upcoming 5.18.0 should have fixed more. Do you have a link to your
report? So I can test it.
--
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

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