Re: [sqlite] Bus error with Evolution 3.12.9 and SQLite 3.8.7.4
Am Dienstag, den 30.12.2014, 08:21 -0500 schrieb Richard Hipp: > On Mon, Dec 29, 2014 at 10:37 AM, László Böszörményi (GCS) wrote: > > > it’s not obvious that these might cause such a regression. > > > > I'm the maintainer of SQLite3 in Debian and can't reproduce it on > > AMD64. Even if I've a local mailbox, normal IMAP4 ones and some from > > GMail. OK, other than the updated SQLite3 library I run on a clean > > Jessie. > > Our latest theory is that the problem only arises when /var/tmp runs out of > space. That seems to be a reasonable theory. Looking at `~/.bash_history` I indeed cleaned up `/var/crash/1300`, where my core dump files are stored by corekeeper [1], and only downgraded to SQLite 3.8.7.1 afterward. Upgrading to SQLite 3.8.7.4 again I am unable to reproduce the crash with 2 GB free space on the partition `/var`. I’ll rebuild SQLite now with the fix applied [2] and try to reproduce the issue by filling up `/var` intentionally. Thank you for the awesome support so far! Thanks, Paul [1] https://packages.debian.org/corekeeper [2] https://www.sqlite.org/src/info/776648412c30dce206f1024ff849c2cb025bb006 signature.asc Description: This is a digitally signed message part ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Bus error with Evolution 3.12.9 and SQLite 3.8.7.4
Am Montag, den 29.12.2014, 16:37 +0100 schrieb László Böszörményi (GCS): > On Mon, Dec 29, 2014 at 2:09 PM, Paul Menzel wrote: > > 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]. > > Just for the record, do you have an Intel or AMD type of CPU? My CPU model is AMD E-350D APU with Radeon(tm) HD Graphics. I am using a 32-bin Linux kernel and userspace. $ uname -m i686 […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Bus error with Evolution 3.12.9 and SQLite 3.8.7.4
On Mon, Dec 29, 2014 at 10:37 AM, László Böszörményi (GCS)wrote: > > > it’s not obvious that these might cause such a regression. > I'm the maintainer of SQLite3 in Debian and can't reproduce it on > AMD64. Even if I've a local mailbox, normal IMAP4 ones and some from > GMail. OK, other than the updated SQLite3 library I run on a clean > Jessie. > Our latest theory is that the problem only arises when /var/tmp runs out of space. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Bus error with Evolution 3.12.9 and SQLite 3.8.7.4
On Mon, Dec 29, 2014 at 2:09 PM, Paul Menzelwrote: > 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]. Just for the record, do you have an Intel or AMD type of CPU? > it’s not obvious that these might cause such a regression. I'm the maintainer of SQLite3 in Debian and can't reproduce it on AMD64. Even if I've a local mailbox, normal IMAP4 ones and some from GMail. OK, other than the updated SQLite3 library I run on a clean Jessie. Laszlo/GCS ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Bus error with Evolution 3.12.9 and SQLite 3.8.7.4
On Mon, Dec 29, 2014 at 9:46 AM, Simon Slavinwrote: > > On 29 Dec 2014, at 1:09pm, Paul Menzel > wrote: > > > 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]. > > Attachments don't work on this list. Please post long text on a web site > somewhere or append it to your message. > > Can you tell what sqlite_ call was being made to cause the crash ? If it > was executing a SQL command, can you tell us what the command is ? > I can see his stack trace by clicking on the bugzilla links, Simon. But, unfortunately, I don't have any clue about what might be the problem. Paul: If you can send a link to the "camel-db.c" source file (part of Evolution, not SQLite), that might be helpful. Note that I'm not blaming camel-db.c but it is in a suspicion-arousing position in the stack trace and I'd like to look closer. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Bus error with Evolution 3.12.9 and SQLite 3.8.7.4
On 29 Dec 2014, at 1:09pm, Paul Menzelwrote: > 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]. Attachments don't work on this list. Please post long text on a web site somewhere or append it to your message. Can you tell what sqlite_ call was being made to cause the crash ? If it was executing a SQL command, can you tell us what the command is ? Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Bus error with Evolution 3.12.9 and SQLite 3.8.7.4
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 6fd550f5b0ee7ed. * 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 signature.asc Description: This is a digitally signed message part ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users