From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27147 invoked by alias); 26 Jun 2012 16:46:32 -0000 Received: (qmail 27107 invoked by uid 22791); 26 Jun 2012 16:46:26 -0000 X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_HELO_PASS,TW_SV,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 26 Jun 2012 16:46:13 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SjYu2-0000IV-D1 for cygwin@cygwin.com; Tue, 26 Jun 2012 18:46:10 +0200 Received: from pd9eb2921.dip.t-dialin.net ([217.235.41.33]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jun 2012 18:46:10 +0200 Received: from Stromeko by pd9eb2921.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jun 2012 18:46:10 +0200 To: cygwin@cygwin.com From: Achim Gratz Subject: Re: cygwin 1.7.15: svn disk I/O error Date: Tue, 26 Jun 2012 16:46:00 -0000 Message-ID: <87ehp2ja2k.fsf@Rainer.invalid> References: <87pq8vxaok.fsf@Rainer.invalid> <4FE117BA.1020909@etr-usa.com> <87395qh7wm.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-06/txt/msg00480.txt.bz2 Achim Gratz writes: > Cygwin should (and apparently does) abstract away that difference. But > it seems that the locking strategy might be slightly different between > Win32 and POSIX, triggering a foray into that "disk I/O error" branch. > There may still be a bug some place else, i.e. it may get a timeout > rather than a "file locked" state. I'll have a look when I find some > time. I've had a look at the sources and those two error messages are with near certainty generated by SQLite. Unfortunately there are many places where they could be generated, it would certainly help if it could be traced where exactly in SQLite this is happening (must be at least two places, maybe more). I've tried to re-build svn against the new SQLite library, but I'm not sure if that works correctly on my machine (the tests are still runnning and I get some test failures already since apparently I'm still missing some dependencies). However, I don't have TortoiseSVN installed anyway. David Rothenberger, I'd appreciate if you could try to do another build of svn and tell us if there are any test regressions w.r.t to your last build. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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