Yes, it appears to also happen on 3.8.10-2. I tested by building pysqlite and replacing python's sqlite3 module with that, statically linked against the current amalgamation release from sqlite.org. I used the stack trace for 14.04's sqlite v3.8.2 since I could more easily install python-dbg for the debug info.
> Date: Tue, 7 Jul 2015 08:19:53 -0400 > From: drh at sqlite.org > To: sqlite-users at mailinglists.sqlite.org > Subject: Re: [sqlite] SIGSEGV rolling back in-memory DB?? > > On 7/6/15, Brian Soby <sobyone at gmail.com> wrote: > > Related to this bug: https://code.djangoproject.com/ticket/24080 > > > > I can reliably duplicate on Ubuntu 14.04 (package details at bottom) but I > > can't seem to create a stripped codebase to repro the issue. GDB stacktrace > > and package details are below. This only appears to happen for in-memory > > databases during a call to read the journal. > > > > There's been a lot of water under the bridge since SQLite 3.8.2. (A > diff of the "sqlite3.c" file for 3.8.2 against the current trunk is > 91,966 lines long.) Have you tried against a more recent version of > SQLite? > > -- > D. Richard Hipp > drh at sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
