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 Message-Id: <200501101836.j0AIaG9m007168@thor.remedy.nl> From: "Johnny Willemsen" To: Subject: RE: problem in pthread_key_create Date: Mon, 10 Jan 2005 19:36:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-0.9 required=5.0 tests=EMAIL_ATTRIBUTION,FORGED_MUA_OUTLOOK,MISSING_OUTLOOK_NAME, MSGID_HAS_NO_AT,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1, SIGNATURE_LONG_SPARSE,UNSUB_PAGE version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Hi Corinna, Thanks for the info. You are right, an EBUSY is returned when a valid key is passed. I wrote first the report about EBUSY, then after that of the ! Part. But, why EBUSY and not EINVAL? I have not figured out why a regression test in ACE (see www.cs.wustl.edu/~schmidt) calls this twice. We now get the error in our logfile: ACE_Thread::keycreate: Device or resource busy (no more keys) I would have expected: ACE_Thread::keycreate: Invalid value. I find the error text so strange. Johnny **** 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.h tml > > 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/ -- 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/