This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: Is cygnus multithreadability usable?
- To: Cygwin at Sourceware dot Cygnus dot Com
- Subject: Re: Is cygnus multithreadability usable?
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Tue, 18 Jul 2000 15:18:57 -0400
- References: <85256920.0066081D.00@nyc-ntgw-n01.ny.jpmorgan.com>
- Reply-To: cygwin at sources dot redhat dot com
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@us.ibm.com on 2000.07.18 14:18:40
>
>To: cygwin@sourceware.cygnus.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:
><abcxyz
>
>>
>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@sourceware.cygnus.com