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=W9eZy8s1xE0Pj4XK
	a0QJND5DsyLJWUwUxK/84brv8rRf5BaYZNK1EQSIoJ7j6jiPtbFEmnwpc8fk60VQ
	KXPz0tkKKGMPkGFITmzQOJ+olzWk7GpIBNejrJ1AplY1vmcwfWtmt7Rszs9E7jo/
	sQJddHL28guQTi1+h2kgZimAqRw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <CAHiT=DF6cbpKLqON+OwVz_5m9fkW00mYB759GzDPMQLpJ2LCYA@mail.gmail.com>
References: <B8D164BED956C5439875951895CB4B22110B04EC@WABOTH9MSGUSR8C.ITServices.sbc.com>	<CAHiT=DF6cbpKLqON+OwVz_5m9fkW00mYB759GzDPMQLpJ2LCYA@mail.gmail.com>
Date: Mon, 20 May 2013 19:22:45 -0700
Message-ID: <CAA5t8VrrFz1ScK2ipbEX=ipHAnYvahzUphDWn9vHOZCtE7+m=Q@mail.gmail.com>
Subject: Re: Were the Perl multithreading problems ever fixed?
From: David Karr <davidmichaelkarr@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

(Resending because it complained about my inadvertently using html.)

My Cygwin Perl is 5.14.2.  I don't have a link to a report.  I never
filed a bug report, but we had an email exchange about this starting
on 1/13/12.  My script is still having occasional problems, but it's
not dumping core.  I'll have to do some more debugging to see what I
can see.

On Mon, May 20, 2013 at 7:10 PM, Reini Urban <rurban@x-ray.at> wrote:
> 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
>

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