This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: CYGWIN 1.5.9-1 - Is vprintf() not thread safe?
- From: Brian Ford <ford at vss dot fsi dot com>
- To: John William <jw2357 at hotmail dot com>
- Cc: cygwin at cygwin dot com
- Date: Fri, 21 May 2004 11:19:40 -0500
- Subject: Re: CYGWIN 1.5.9-1 - Is vprintf() not thread safe?
- References: <BAY1-F44GxqymcgfyDy000249a4@hotmail.com>
- Reply-to: cygwin at cygwin dot com
On Fri, 21 May 2004, John William wrote:
> >From: Brian Ford <ford@SNIP>
> >To: John William <jw2357@SNIP>
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/