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 X-Authenticated: #623905 Message-ID: <40AE66A3.7080308@gmx.net> Date: Fri, 21 May 2004 22:29:23 +0200 From: Thomas Pfaff 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: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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/