X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 18 Mar 2010 15:53:01 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.7: Concurrency Issue with Shared State Initialization Message-ID: <20100318195301.GA12873@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: 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 Thu, Mar 18, 2010 at 03:55:48PM +0100, Schmidt, Oliver wrote: >Hi Corinna, > >> Would you mind to give the latest developer snapshot from >> http://www.cygwin.com/snapshots/ a try? It tries very carefully to >> eliminate concurrency problems in the initialization phase. > >I see. With the same scenario as in my original posting I trigger an >assertion added by Christopher the other day: > >assertion "*native_root != '\0'" failed: file "/netrel/src/cygwin-snapshot-20100315-1/winsup/cygwin/mount.cc", line 341, function: void mount_info::create_root_entry(WCHAR*) 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. 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