This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: sqlite defect


On 2013-07-19 PM 8:30, Corinna Vinschen wrote:
A valid testcase would help a lot, though.  What you meant to do
was calling flock with LOCK_EX|LOCK_NB.

that's what exactly sqlite3 that uses the mandatory-locking did. reproducing the behavior was i meant to do.
And then again, your testcase works as designed.  Not by me, but by
Microsoft.  You can't overwrite an existing lock, even if hold by the
same file handle.  See http://cygwin.com/cygwin-api/std-notes.html

Yes. the testcase works without mandatory locking. so i hope next sqlite3 release doesn't use mandatory locking feature of cygwin. someone who have plenty of time to waste digging into sqlite3 source code would come with workaround to the problem.

Corinna



--
Regards.


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]