Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Authenticated:	#623905
Message-ID:	<40AE66A3.7080308@gmx.net>
Date:	Fri, 21 May 2004 22:29:23 +0200
From:	Thomas Pfaff <tpfaff AT gmx DOT net>
User-Agent:	Mozilla Thunderbird 0.5 (X11/20040208)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: CYGWIN 1.5.9-1 - Is vprintf() not thread safe?
References:	<BAY1-F44GxqymcgfyDy000249a4 AT hotmail DOT com> <Pine DOT CYG DOT 4 DOT 58 DOT 0405211113290 DOT 3524 AT fordpc DOT vss DOT fsi DOT com>
In-Reply-To:	<Pine.CYG.4.58.0405211113290.3524@fordpc.vss.fsi.com>

Brian Ford wrote:
> On Fri, 21 May 2004, John William wrote:
>>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.
> 

You took the words right out of my mouth.

Thomas

--
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/

- Raw text -