From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31396 invoked by alias); 28 Jun 2012 21:17:17 -0000 Received: (qmail 31386 invoked by uid 22791); 28 Jun 2012 21:17:16 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,TW_SV,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from etr-usa.com (HELO etr-usa.com) (130.94.180.135) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 28 Jun 2012 21:17:04 +0000 Received: (qmail 52628 invoked by uid 13447); 28 Jun 2012 21:17:03 -0000 Received: from unknown (HELO [172.20.0.42]) ([71.210.206.161]) (envelope-sender ) by 130.94.180.135 (qmail-ldap-1.03) with SMTP for ; 28 Jun 2012 21:17:03 -0000 Message-ID: <4FECC9C7.7070708@etr-usa.com> Date: Thu, 28 Jun 2012 21:17:00 -0000 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Cygwin-L Subject: Re: cygwin 1.7.15: svn disk I/O error References: <87pq8vxaok.fsf@Rainer.invalid> <4FE117BA.1020909@etr-usa.com> <87395qh7wm.fsf@Rainer.invalid> <87ehp2ja2k.fsf@Rainer.invalid> <4FE9F08A.9060503@acm.org> <87a9zqj6b7.fsf@Rainer.invalid> <4FEB4E48.8090600@acm.org> <87sjdfs14p.fsf@Rainer.invalid> <4FECB891.20908@etr-usa.com> <87fw9frx87.fsf@Rainer.invalid> In-Reply-To: <87fw9frx87.fsf@Rainer.invalid> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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/msg00549.txt.bz2 On 6/28/2012 2:35 PM, Achim Gratz wrote: > I can't easily test this myself > since I don't have TortoiseSVN installed Me, too, but it seems to me that there's a better way to find the problem than trying to replicate the problem reporters' exact environment. That's too complicated. The leading hypothesis explaining the problem is that there's a file locking problem between two programs both trying to access the same set of SQLite DB files. So, write two programs to do exactly that, and see if they will fight over the DB file or not. If they cooperate, as the SQLite FAQ says they should, then we're off in the weeds and someone needs to come up with a better hypothesis. If they fight, you then have two simple programs that, together, demonstrate the problem, which means you're much closer to finding a real fix that makes both sets of users happy. Take advantage of the fact that I'm a disinterested Cygwin package maintainer. You have some time to play with here. -- 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