On Thu, Sep 10, 2015 at 4:58 PM, Scott Hess <shess at google.com> wrote: > > The same basic logic applies to sqlite3_initialize()'s testing and setting > of sqlite3GlobalConfig.isInit , in a different thread+core the test can see > "true" before that core sees the setup implied by isInit being set to > "true". >
BTW, I _think_ this is broadly the problem in double-checked locking documents where the reference to the instance is correctly accessed, but the instance itself is not guaranteed to be fully constructed in the case of the unlocked check. -scott