From: mka@redes.int.com.mx (Michael Anderson) Subject: Re: Thread-safeness in cygwin32 21 Nov 1997 17:02:56 -0800 Message-ID: <34759B87.29AA39B8.cygnus.gnu-win32@redes.int.com.mx> References: <199711211000.CAA19889@rtl.cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Geoffrey Noer Cc: gnu-win32@cygnus.com Geoffrey Noer wrote: > Unfortunately it (B18) is not thread-safe and b19 won't be either when > it comes out. Newlib does make some attempts at minimizing race conditions > but it isn't thread-safe. The rest of the code in cygwin.dll from the > winsup directory would also need a lot of reworking. Sorry... :-( Thanks Geoffrey for confirming this. The other part of my question is about the process-safeness of B18. Can one process corrupt another through the common use of cygwin.dll or otherwise? -- Mike Anderson mka@redes.int.com.mx Guanajuato, GTO, Mexico - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".