Dear Evolution and SQLite folks,
using Debian Sid/unstable and upgrading from libsqlite3-0 3.8.7.2 to
3.8.7.4, Evolution 3.12.9 started to crash with a bus error [1].
After downgrading to SQLite 3.8.7.1 from Debian Jessie/testing I was
unable to reproduce the issue.
Looking at the changelog [2]
2014-12-09 (3.8.7.4)
* Bug fix: Add in a mutex that was omitted from the previous
release.
* SQLITE_SOURCE_ID: "2014-12-09 01:34:36
f66f7a17b78ba617acde90fc810107f34f1a1f2e"
* SHA1 for sqlite3.c: 0a56693a3c24aa3217098afab1b6fecccdedfd23
2014-12-06 (3.8.7.3)
* Bug fix: Ensure the cached KeyInfo objects (an internal
abstraction not visible to the application) do not go stale when
operating in shared cache mode and frequently closing and
reopening some database connections while leaving other database
connections on the same shared cache open continuously. Ticket
e4a18565a36884b00edf.
* Bug fix: Recognize that any column in the right-hand table of a
LEFT JOIN can be NULL even if the column has a NOT NULL
constraint. Do not apply optimizations that assume the column is
never NULL. Ticket 6f2222d550f5b0ee7ed.
* SQLITE_SOURCE_ID: "2014-12-05 22:29:24
647e77e853e81a5effeb4c33477910400a67ba86"
* SHA1 for sqlite3.c: 3ad2f5ba3a4a3e3e51a1dac9fda9224b359f0261
it’s not obvious that these might cause such a regression.
Please find the backtraces attached to the bug reported in the GNOME
Bugzilla [1].
Thanks,
Paul
PS: I have not submitted a bug report to the Debian BTS yet, as I do not
know if it is a bug in Evolution or SQLite 3 and I want to avoid a false
assignment as done by myself in [3].
[1] https://bugzilla.gnome.org/show_bug.cgi?id=742080
[2] http://www.sqlite.org/changes.html
[3] https://bugzilla.gnome.org/show_bug.cgi?id=738965
Attachment:
signature.asc
Description: This is a digitally signed message part