I don't believe it's a python specific issue since the core problem occurs in a rollback command internal to SQLlite. I don't have an easy way to recreate the problem since it takes quite a bit of app code to run the test suite that triggers the problem. I can however provide any output of anything you'd like.
> Date: Tue, 7 Jul 2015 12:47:48 -0400 > From: drh at sqlite.org > To: sqlite-users at mailinglists.sqlite.org > Subject: Re: [sqlite] SIGSEGV rolling back in-memory DB?? > > On 7/7/15, Brian Soby <sobyx at hotmail.com> wrote: > > 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. > > > > Can you send instructions on how to recreate the problem? Please bare > in mind that none of the core SQLite developers do much with python. > Alternatively, you might send emails to Roger Binns and badger him > into trouble-shooting the problem, since he is an expert at both > python and SQLite and is likely to get to the bottom of the matter > faster than any of the core SQLite devs. > > -- > 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
