X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-SBRS: None X-MesageID: 32249413 X-Ironport-Server: ftlpip01.citrite.net X-Remote-IP: 70.42.232.150 X-Policy: $Relay X-IronPort-AV: E=Sophos;i="4.21,378,1188792000"; d="scan'208";a="32249413" Date: Tue, 6 Nov 2007 15:56:34 +0000 From: Samuel Thibault To: cygwin AT cygwin DOT com Subject: Re: why is pthread_key_create failing? Message-ID: <20071106155634.GK3795@implementation.uk.xensource.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <200711061512 DOT 15518 DOT bruno AT clisp DOT org> <20071106153026 DOT GA1203 AT calimero DOT vinschen DOT de> <20071106154550 DOT GB1203 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20071106154550.GB1203@calimero.vinschen.de> User-Agent: Mutt/1.5.12-2006-07-14 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Hi, Corinna Vinschen, le Tue 06 Nov 2007 16:45:50 +0100, a écrit : > Heh, I just re-read the whole discussion at > http://www.mail-archive.com/cygwin%40cygwin.com/msg49835.html again, > and it's interesting how the point of view changes with another > testcase. Pity. Returning EBUSY really looked like a good idea. Mmm, the "Non-Idempotent Data Key Creation" section only says that some behavior was rejected because there is other ways to achieve it. But to me it does not mean that EBUSY would be a good idea. What explicitely says that you shouldn't reuse a pthread_key_t? Samuel -- 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/