DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 538EwHKJ2124088
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9FA003858D35
Date: Tue, 8 Apr 2025 23:57:47 +0900
To: cygwin@cygwin.com
Subject: Re: Deadlock when calling pthread_key_create in the destructor of a
 pthread_key
Message-Id: <20250408235747.fcae7b1a340830f3d445c1c8@nifty.ne.jp>
In-Reply-To: <TYCPR01MB1092618CD4D65CA5AA26F73FAF8A52@TYCPR01MB10926.jpnprd01.prod.outlook.com>
References: <TYCPR01MB1092618CD4D65CA5AA26F73FAF8A52@TYCPR01MB10926.jpnprd01.prod.outlook.com>
Mime-Version: 1.0
Precedence: list
From: Takashi Yano via Cygwin <cygwin@cygwin.com>
Reply-To: Takashi Yano <takashi.yano@nifty.ne.jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

On Sun, 23 Mar 2025 20:32:44 +0800
Yuyi Wang wrote:
> It's a bug when I tried to run tests of Rust std lib. The standard
> library of Rust tries to create a new pthread_key in the destructor of a
> key created previously. Unfortunately, List::for_each locked the mutex
> before, so List_insert method cannot lock the mutex again.
> 
> I have searched though the POSIX docs and didn't find any words that one
> should not call pthread_key_create in the destructor of a pthread_key. I
> think it should be a bug of cygwin.

Fixed. Please try cygwin-3.7.0-0.49.g42df80dad079.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple