This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: sqlite defect
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 18 Jul 2013 10:59:53 +0200
- Subject: Re: sqlite defect
- References: <trinity-fdc5a0b5-6dcf-4fc0-9370-dd32a75fe928-1373654994500 at 3capp-gmx-bs47> <51E703FB dot 1010300 at etr-usa dot com> <trinity-1068d666-3dec-43c9-8453-39c7cae3a94c-1374102947415 at 3capp-gmx-bs33> <51E74AB4 dot 7010508 at etr-usa dot com> <ks87ur$nle$1 at ger dot gmane dot org>
- Reply-to: cygwin at cygwin dot com
On Jul 18 17:11, jojelino wrote:
> On 2013-07-18 AM 10:53, Warren Young wrote:
> >Nothing so simple. Locking is handled at the OS and/or Cygwin DLL
> >level. The build change between 3.7.16.2 and 3.7.17-3 is that we're now
> >relying on new features in the Cygwin DLL to do Windows-style locking by
> >default.
> >
> >Older versions of Cygwin SQLite bypassed the Cygwin DLL entirely for
> >this, going straight to the Win32 API, thereby preventing the DLL from
> >interposing itself for the "posix" case.
> >
> Mandatory locking feature of cygwin used in sqlite is broken.
Simple testcase in plain C?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer 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