Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <002b01c0d490$08166b40$26823bd5@dima> From: "Dmitry Timoshkov" To: "egor duda" Cc: References: <002901c0d47c$255059f0$78752ec3 AT dima> <19328203691 DOT 20010504123612 AT logos-m DOT ru> Subject: Re: oldhand cygwinner needed: RE: __errno_location() like functionality in Cygwin Date: Fri, 4 May 2001 19:47:37 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-MDRcpt-To: cygwin AT cygwin DOT com X-MDRemoteIP: 213.59.130.38 X-Return-Path: dmitry AT sloboda DOT ru X-MDaemon-Deliver-To: cygwin AT cygwin DOT com "egor duda" wrote: > >> As for errno in cygwin I'm not sure off the top of my head as to it's > >> thread safeness... comments anyone? > > DT> That is the core of my question. > > use the source, Luke :) it is. Thanks for the pointer, but did you see my original question? How can I have *only* thread local errno variable? Under Linux that functionality is provided by overriding __errno_location() function. Under Cygwin definition of my own __errno() function doesn't help. And regarding the pointed out code: int * __errno () { return &_REENT->_errno; } That means, that multithreaded application must set global variable _REENT before every libc call. No? Perhaps my understanding of things is completely wrong? Any other suggestions? Kind regards. -- Dmitry. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple