X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4B08376D.9060408@gmail.com>
Date: Sat, 21 Nov 2009 18:54:37 +0000
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: [OT] Re: Use of Dual Core causes random failures building OpenJDK
References: <4B061709 DOT 2040507 AT cygwin DOT com> 	 <20091120144958 DOT GW29173 AT calimero DOT vinschen DOT de> 	 <b0ddfae80911201019m4832a7f9k684b502b52a05ce3 AT mail DOT gmail DOT com> 	 <20091120184906 DOT GA27241 AT ednor DOT casa DOT cgf DOT cx> 	 <b0ddfae80911201104g705e4a1bkb2bd526a50eb8ea2 AT mail DOT gmail DOT com> 	 <20091121121218 DOT GZ29173 AT calimero DOT vinschen DOT de> 	 <b0ddfae80911210516t36d42aadj6496b054a9f694c8 AT mail DOT gmail DOT com> 	 <20091121173625 DOT GB9003 AT ednor DOT casa DOT cgf DOT cx> 	 <b0ddfae80911211004j3046a795y9ab3a3ba7374a859 AT mail DOT gmail DOT com> 	 <4B083047 DOT 8050101 AT gmail DOT com> <b0ddfae80911211027t6f912979ic1fbf2d31aa4441 AT mail DOT gmail DOT com>
In-Reply-To: <b0ddfae80911211027t6f912979ic1fbf2d31aa4441@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

mike marchywka wrote:

> On XP, go to control panel->System->Advanced ->Envireonment Variables.
> These do no appear to be process specific. These are what I was talking
> about where I saw garbage, 

  Since registry accesses are atomic and serialized, whatever you saw there
must reflect exactly the gibberish that some process wrote into the registry,
owing to a bug in that process (or maybe in some hook process, or faulty ram
or other hardware in your PC); it was not the outcome of two threads trying to
write to the registry at the same time.

  And, as indeed you hypothesize, none of this is to do with Cygwin, so we
should TITTTL if there's anything else you want to ask about the windows
environment block and how it is implemented and handled in a thread-safe and
process-safe fashion; I don't mind going into further detail if you're
curious, but I want to leave the main list out of it now.

    cheers,
      DaveK


--
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