Crash in geary_db_connection_exec_transaction()
This backtrace is not very good because I was running under valgrind hoping I'd get lucky enough to discover the cause of a previous Geary crash (that I didn't report, because it was due to memory corruption). Anyway, I failed in that goal, but I did find a much simpler crash:
==21388== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==21388== Access not within mapped region at address 0xB8
==21388== at 0xA2CDB47: getPageNormal (sqlite3.c:55838)
==21388== by 0xA2AB7C1: sqlite3PagerGet (sqlite3.c:56001)
==21388== by 0xA2AB7C1: getAndInitPage (sqlite3.c:65047)
==21388== by 0xA2D4CB3: sqlite3BtreeMovetoUnpacked (sqlite3.c:68454)
==21388== by 0xA2FB219: sqlite3VdbeExec (sqlite3.c:86984)
==21388== by 0xA2FFFAF: sqlite3Step (sqlite3.c:81340)
==21388== by 0xA2FFFAF: sqlite3_step (sqlite3.c:81403)
==21388== by 0xA2FFFAF: sqlite3_step (sqlite3.c:81391)
==21388== by 0x79CED0: geary_db_result_next (db-result.vala:39)
==21388== by 0x79CB6F: geary_db_result_construct (db-result.vala:19)
==21388== by 0x79CBE3: geary_db_result_new (db-result.vala:13)
==21388== by 0x7A2045: geary_db_statement_exec (db-statement.vala:120)
==21388== by 0x6A24A3: __lambda83_ (imap-db-account.vala:634)
==21388== by 0x6A3074: ___lambda83__geary_db_transaction_method (imap-db-account.c:6767)
==21388== by 0x795D4E: geary_db_connection_exec_transaction (db-connection.vala:403)