X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 16 Aug 2012 10:50:16 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Promote sqlite 3.7.13-1 from test status? (was: Updated: sqlite3-3.7.13-1) Message-ID: <20120816085016.GB5536@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <502C0B7D DOT 10909 AT etr-usa DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 Aug 16 07:41, Achim Gratz wrote: > Warren Young etr-usa.com> writes: > > I haven't heard peep one from either side about this release on this > > list. (For contrast, I've gotten several positive responses in my > > answer to the question about this on Stack Overflow[1].) > > Sorry, I've been swamped with other stuff... > > > Silence = happiness, then? :) > > The original bug is back, although it behaves even more wierd than before. The > error now happens _only_ when run as normal user _and_ not under strace or gdb. > > $ sqlite3 > SQLite version 3.7.13 2012-06-11 02:05:22 > Enter ".help" for instructions > Enter SQL statements terminated with a ";" > sqlite> CREATE TEMP TABLE two (id INTEGER NOT NULL, name CHAR(64) NOT NULL ); > Error: unable to open database file > sqlite> > > Since I can't reproduce the problem in the debugger anymore, it will be > difficult to impossible to find out what's causing this (at least for me). Just > like the problem with TortoiseSVN these are indications IMHO that there's a race > somewhere between calls from the Cygwin DLL and Windows file locking functions. Cygwin does not use Windows mandatory locking. The locking is entirely implemented within the Cygwin DLL and is only advisory, as is befitting for a POSIX envionment. If you try to use the same file with a non-Cygwin tool using Windows locking in parallel with a Cygwin tool, you will get into trouble. The mandatory Windows locking will always win and the Cygwin tool will fail. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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