delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2009/11/21/13:52:07

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 21 Nov 2009 13:50:49 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [OT] Re: Use of Dual Core causes random failures building OpenJDK
Message-ID: <20091121185049.GA13903@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <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> <4B08376D DOT 9060408 AT gmail DOT com>
MIME-Version: 1.0
In-Reply-To: <4B08376D.9060408@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Sat, Nov 21, 2009 at 06:54:37PM +0000, Dave Korn wrote:
>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.

Yes, please take it to the talk list.

In the meantime, I'm going to try teaching my dog to play the piano.

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019