On Mon, Nov 14, 2016 at 12:38 PM, pisymbol . <pisym...@gmail.com> wrote:
> > > On Mon, Nov 14, 2016 at 12:14 PM, pisymbol . <pisym...@gmail.com> wrote: > >> >> >> On Thu, Nov 10, 2016 at 11:52 AM, Richard Hipp <d...@sqlite.org> wrote: >> >>> On 11/10/16, pisymbol . <pisym...@gmail.com> wrote: >>> > sqlite-3.6.20-1.el6_7.2.i686 >>> > sqlite-3.6.20-1.el6_7.2.x86_64 >>> >>> Are you aware that SQLite 3.6.20 was published over 7 years ago on >>> 2009-11-04 and that there have been 82 subsequent releases of SQLite >>> and that the newer releases run more than twice as fast? >>> >>> Maybe the right solution is updated to SQLite 3.15.1? >>> >> >> It could very well be. So it happened again (SIGSEGV) on start up >> Provided my assumption that I'm doing nothing really wrong, I guess I'll >> try static linking a newer version of sqlite3 to see if it disappears >> > > http://sqlite.org/threadsafe.html > > I just realized, that multithreaded mode isn't truly multi-threaded mode > in that two simultaneous threads can not use the same handle! It looks I > need serialized mode > Still happens even in serialized mode. I'm at a loss. -aps _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
