Re: Bug report: Potential thread safety issues in sqlite3_initialize
Richard Hipp <[email protected]>
| Newsgroups | gmane.comp.db.sqlite.general |
|---|---|
| Message-ID | <CALwJ=Mwas5+nEm_v8NUWOMJu8qMWhHU9Hhi9n4XKCzFNNL6Jgw@mail.gmail.com> |
On 1/28/20, Oystein Eftevaag <[email protected]> wrote: > in sqlite3MutexInit() sqlite3GlobalConfig.mutex.xMutexAlloc > can be read as being set on a core, while the rest of the initialization > done in sqlite3MutexInit() still is being read as unset. Doesn't the memory barrier at https://www.sqlite.org/src/artifact/bae36f8af32c22ad?ln=247 prevent that? Do you have a suggested patch to make it work? -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users