From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: cygwin 1.7.15: svn disk I/O error
Date: Fri, 15 Jun 2012 10:38:00 -0000 [thread overview]
Message-ID: <4FDB1069.9060809@etr-usa.com> (raw)
In-Reply-To: <201206142200.q5EM0Td3088427@barrierL241.nike.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
next prev parent reply other threads:[~2012-06-15 10:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 19:48 Rolf Campbell
2012-06-14 19:55 ` Christopher Faylor
2012-06-14 20:09 ` Rolf Campbell
2012-06-14 22:00 ` Garrison, Jim (ETW)
2012-06-14 22:02 ` Garrison, Jim (ETW)
2012-06-15 10:38 ` Warren Young [this message]
2012-06-15 13:24 ` Rolf Campbell
2012-06-15 13:43 ` Rolf Campbell
2012-06-19 9:32 ` Adam Dinwoodie
2012-06-19 19:24 ` Rolf Campbell
2012-06-19 21:19 ` Achim Gratz
2012-06-20 0:22 ` Warren Young
2012-06-20 5:25 ` Achim Gratz
2012-06-26 16:46 ` Achim Gratz
2012-06-26 17:25 ` David Rothenberger
2012-06-26 18:07 ` Achim Gratz
2012-06-27 9:11 ` Adam Dinwoodie
2012-06-27 14:07 ` Achim Gratz
2012-06-27 18:18 ` David Rothenberger
2012-06-27 18:41 ` Achim Gratz
2012-06-28 11:49 ` Achim Gratz
2012-06-28 16:31 ` David Rothenberger
2012-06-28 19:04 ` Achim Gratz
2012-06-28 19:27 ` David Rothenberger
2012-06-28 20:40 ` Achim Gratz
2012-07-11 6:34 ` Achim Gratz
2012-07-11 7:07 ` marco atzeri
2012-07-11 7:48 ` Achim Gratz
2012-07-11 17:19 ` marco atzeri
2012-06-28 17:37 ` Rolf Campbell
2012-06-28 19:11 ` Achim Gratz
2012-06-28 20:03 ` Warren Young
2012-06-28 20:35 ` Achim Gratz
2012-06-28 21:17 ` Warren Young
2012-06-28 20:37 ` David Rothenberger
[not found] <CABVhxxKw8i96668GgHmMyPXCn+nBS8S874Q7wSSHgoer8iiSsw@mail.gmail.com>
2012-08-07 1:10 ` Michael Gundlach
2012-08-07 1:55 ` Warren Young
2012-08-07 1:57 ` Michael Gundlach
2012-08-07 2:42 ` Warren Young
2012-08-07 12:16 ` Michael Gundlach
2012-08-07 17:56 ` David Rothenberger
2012-08-08 13:14 ` Warren Young
2012-08-07 7:00 ` Achim Gratz
2012-08-07 7:38 ` Warren Young
2012-08-07 5:07 ` Christopher Faylor
[not found] ` <CABVhxxJ_nsTF3o85nWJsRdMOq38LYr2R9b9H8ATHfNCCqnmbqw@mail.gmail.com>
2012-08-07 14:05 ` Michael Gundlach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FDB1069.9060809@etr-usa.com \
--to=warren@etr-usa.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).