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: Fri, 21 May 2004 11:19:40 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: John William cc: cygwin AT cygwin DOT com Subject: Re: CYGWIN 1.5.9-1 - Is vprintf() not thread safe? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes On Fri, 21 May 2004, John William wrote: > >From: Brian Ford > >To: John William http://cygwin.com/acronyms/#PCYMTNQREAIYR > >IIRC, several thread safe stdio issues have been fixed recently, both in > >Cygwin and in newlib. Please try a recent Cygwin DLL snapshot: > > > >http://cygwin.com/snapshots/ > > > >and report back. Thanks. > > I tried the cygwin.dll snapshot dated 2004-05-20 and it still outputs > interleaved text with multiple threads and vprintf()/vsprintf() crash when > called from multiple threads and not protected with mutex_lock() and > mutex_unlock() calls around them. This is on a dual-processor system, BTW. How about posting a simple test case. If you do so, I'll try and take a look. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/