X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_05,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <59199.83.86.0.251.1296074767.squirrel@lavabit.com> Date: Wed, 26 Jan 2011 21:46:07 +0100 (CET) Subject: Re: 1.7.7: stdio functions block each other in a multithreaded program From: cornwarecjp AT lavabit DOT com To: cygwin AT cygwin DOT com User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 > [...] > What you can do for the time being is to use the low-level IO functions > read and write, rather than the stdio functions fgetc and putchar, since > only the stdio functions are affected by this. > I hope to find a solution soon and the bugfix will definitely be in 1.7.8. > Again, thanks for testcase. It's highly appreciated. Nice to hear you appreciate it. I can confirm that using the low-level IO function 'read' instead of the scanf function avoids the issue. For now, I will use this approach. So for me the issue is solved. Thanks, and good luck finding a solution for version 1.7.8. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple