X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-10.6 required=5.0 	tests=BAYES_00,RCVD_IN_DNSWL_HI
X-Spam-Check-By: sourceware.org
From: "Schmidt, Oliver" <oliv DOT schmidt AT sap DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date: Fri, 19 Mar 2010 17:59:40 +0100
Subject: Re: Cygwin 1.7: Concurrency Issue with Shared State Initialization
Message-ID: <B10B50309DC54D45A855FD66F56015F71D7B3B0285@DEWDFECCR03.wdf.sap.corp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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

Hi Christopher,

> How about today's snapshot?  Corinna has YA told me what I did wrong with=
 the
> latest round of spinlock changes and today's snapshot reflects her obvious
> fix.

Good news for the weekend! I've been running my original scenario with
20100318 repeatedly all day long. I couldn't reproduce any issue so far :-)

From my perspective you can consider the issue solved. However I'll continue
to run tests next week. If anything goes wrong I'll post another follow-up
here...

Thanks for your very active support in solving this issue with our far from
mainstream scenario!

Regards, Oliver

P.S.: I presume the fix will show up in the next Cygwin release.

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