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 From: Chris Faylor Date: Tue, 18 Jul 2000 15:18:57 -0400 To: Cygwin AT Sourceware DOT Cygnus DOT Com Subject: Re: Is cygnus multithreadability usable? Message-ID: <20000718151857.E26695@cygnus.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: Cygwin AT Sourceware DOT Cygnus DOT Com References: <85256920 DOT 0066081D DOT 00 AT nyc-ntgw-n01 DOT ny DOT jpmorgan DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <85256920.0066081D.00@nyc-ntgw-n01.ny.jpmorgan.com>; from yap_noel@jpmorgan.com on Tue, Jul 18, 2000 at 02:34:31PM -0400 On Tue, Jul 18, 2000 at 02:34:31PM -0400, Noel L Yap wrote: >I think printf(), by definition, is not threadsafe. The caller is responsible >for making threadsafe calls to it. Right. cgf >kulack AT us DOT ibm DOT com on 2000.07.18 14:18:40 > >To: cygwin AT sourceware DOT cygnus DOT com >cc: (bcc: Noel L Yap) >Subject: Re: Is cygnus multithreadability usable? > >> Multithread-safe support is turned on by default in 1.1.x releases. >> That does not mean that it is bug free. >> cgf >Interesting. I was using just a minimal amound of C runtime stuff (mainly >printf), and noticed thread safety problems so I just assumed it wasn't >safe. For my projects, it didn't matter much, but now that you mention the >above, it might just be a simple bug. > >Thread 1: >printf("abc\n"); > >Thread 2: >printf("xyz\n") > >Frequently results in the newlines intermingling: > >> >On one occasion I believe that the output was more mixed than that, but I >could be making that up... 8-) -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com