On 19 Jul 2012, at 5:09pm, Rick Maddy <rma...@gmail.com> wrote: > Exception Type: SIGSEGV > Exception Codes: SEGV_ACCERR at 0x1a
Those are segfaults. They indicate an attempt by your app to access memory which doesn't belong to it. This often but not always happens because the memory /did/ once belong to it but has now been released. First, run <http://www.sqlite.org/pragma.html#pragma_integrity_check> to see if your database is corrupt. Then put checks in your code for result codes every time you call a function of the SQLite API. For instance, sqlite3_prepare_v2() returns a result code you should be checking. Just asserting that the int returned is SQLITE_OK will probably be enough. While putting the checks in, you'll probably notice whatever's causing your bug. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
