X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sat, 21 Nov 2009 12:36:25 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Use of Dual Core causes random failures building OpenJDK Message-ID: <20091121173625.GB9003@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4B061709 DOT 2040507 AT cygwin DOT com> <20091120112052 DOT GT29173 AT calimero DOT vinschen DOT de> <20091120143237 DOT GD18289 AT ednor DOT casa DOT cgf DOT cx> <20091120144958 DOT GW29173 AT calimero DOT vinschen DOT de> <20091120184906 DOT GA27241 AT ednor DOT casa DOT cgf DOT cx> <20091121121218 DOT GZ29173 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sat, Nov 21, 2009 at 08:16:29AM -0500, mike marchywka wrote: >On 11/21/09, Corinna Vinschen wrote: >>No, never. If there is a concurrency problem with the envionment, it's >>between threads of the same process. In that case, we can make getenv, >>setenv and friends thread-safe, but it's still actually a problem of >>the application, given that getenv, setenv and friends are not >>thread-safe per POSIX. See >>http://www.opengroup.org/onlinepubs/9699919799/functions/setenv.html >>http://www.opengroup.org/onlinepubs/9699919799/functions/getenv.html >>http://www.opengroup.org/onlinepubs/9699919799/functions/unsetenv.html >> > >well, the question was somewhat rhetorical/disingenuous but I don't see >how in the general case then the OS can allow two simultaneous >processes to modify windoze env variables in a way that corrupts them. >The app is responsible for itself but I'm not sure what it can do with >respect to other processes. If you wanted an emulation layer to be >safe you are still limited by the OS( but you may have already known >that LOL). I am beginning to think that this is a troll. Corinna talks about threads and you talk about processes. Either you're clueless about the distinction or you are just "having fun". There are simple things that can be done to make Cygwin's handling of environment variables thread safe. Stop arguing about it. You're just looking stupid now. cgf -- 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