Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 10 Jan 2005 13:38:10 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Problem in pthread_key_create Message-ID: <20050110123810.GG7748@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200501091731 DOT j09HVm9m000706 AT thor DOT remedy DOT nl> <20050110120007 DOT GF7748 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050110120007.GF7748@cygbert.vinschen.de> User-Agent: Mutt/1.4.2i On Jan 10 13:00, Corinna Vinschen wrote: > On Jan 9 18:31, Johnny Willemsen wrote: > > A question, I had a look at the implementation of pthread_key_create. When > > an invalid key is passed, a EBUSY is returned. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I just read this again and it occured to me that this is a misconception. pthread_key_create() returns EBUSY if a *valid* key is passed. This should make it clearer, shouldn't it? Corinna > > No, that's not a bug. Please read the SUSv3 description for > pthread_key_create() here: > > http://www.opengroup.org/onlinepubs/009695399/functions/pthread_key_create.html > > Please note especially the chapter > > RATIONALE/Non-Idempotent Data Key Creation. > [...] -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/