Overview
Artifact ID: | e93ae3ff2a461c5a9cdce3eef2483a4bb11f79c5 |
---|---|
Ticket: | f46ca03b55ae0ecab698c623031abbb550e1f405
The order of two operations in asyncLock() |
User & Date: | anonymous 2012-11-29 08:31:34 |
Changes
- comment changed to:
In file sqlite3async.c, the function asyncLock(), line 888 Why set the lock.eLock and lock.eAsyncLock before getFileLock() is called? If getFileLock() failed, why not reset the eLock and eAsyncLock? It looks like if the first asyncLock() called failed, the second will succeed without any check?
- Untracked field detected: "Code_Review"
- foundin changed to: "3.7.14.1"
- private_contact changed to: "7775aa316ff01dfe638bbf525a453db28dc737a8"
- severity changed to: "Important"
- status changed to: "Open"
- subsystem changed to: "Extensions"
- title changed to: "The order of two operations in asyncLock()"