X-Recipient: archive-cygwin AT delorie DOT com
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
Message-ID: <4FDB1069.9060809@etr-usa.com>
Date: Fri, 15 Jun 2012 04:37:29 -0600
From: Warren Young <warren AT etr-usa DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0
MIME-Version: 1.0
To: Cygwin-L <cygwin AT cygwin DOT com>
Subject: Re: cygwin 1.7.15: svn disk I/O error
References: <jrdf56$61r$1 AT dough DOT gmane DOT org> <20120614195507 DOT GA13195 AT ednor DOT casa DOT cgf DOT cx> <201206142200 DOT q5EM0Td3088427 AT barrierL241 DOT nike DOT com>
In-Reply-To: <201206142200.q5EM0Td3088427@barrierL241.nike.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

On 6/14/2012 4:00 PM, Garrison, Jim (ETW) wrote:
>> Why would you think that a disk I/O error was either anti-virus or
>> Cygwin related and not... a disk I/O error?  Have you looked in your
>> event logs for errors?
>
> It is indeed AV related -- a race between SQLite and AV

That's one possibility, but check this out:

	http://stackoverflow.com/questions/11007024/

tl;dr: someone made the problem go away by rolling my recent 3.7.12 
release back to the prior 3.7.3 version.

I doubt the problem is in the upstream changes between .3 and .12.  I'm 
more worried about the build option changes.  SQLite has a lot of 
Windows-specific code in it, plus some Cygwin-specific code, too.  The 
build changes override some things to force it to believe it's being 
built for a more generic POSIX type system.

It may be both things: the build option changes that force more I/O 
calls to go through Cygwin instead of direct to the Win32 API could be 
tickling BLODA bugs.

Yet another possibility is that the build option changes cause a subtle 
ABI change that will be fixed when SVN is rebuilt against it.

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