delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
From: | kulack AT us DOT ibm DOT com |
X-Lotus-FromDomain: | IBMUS |
To: | cygwin AT sourceware DOT cygnus DOT com |
Message-ID: | <85256920.006493B6.00@D51MTA04.pok.ibm.com> |
Date: | Tue, 18 Jul 2000 13:18:40 -0500 |
Subject: | Re: Is cygnus multithreadability usable? |
Mime-Version: | 1.0 |
> 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 AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |