On 10/29/2011 03:00 PM, Alexandre Courbot wrote:
Hi everybody,
While testing some database upgrade function of mine, I ran into a
segmentation fault. I started looking at the possible cause in my
code, but I soon realized the crash would only happen using SQLite
3.7.7 or 3.7.8. If I use 3.7.6 or lower, things go safely.
Since I am not familiar with SQLite's internals, I have run the thing
under Valgrind and GDB to get some backtraces. Here is Valgrind's
report:
And here is the GDB backtrace (using 3.7.8):
#0 0x0000000000646251 in sqlite3Fts3PendingTermsFlush (p=0x0) at
sqlite3.c:124996
#1 0x000000000063a2a9 in fts3SyncMethod (pVtab=0x0) at sqlite3.c:117025
#2 0x000000000063a984 in fts3SavepointMethod (pVtab=0x0, iSavepoint=0)
at sqlite3.c:117332
#3 0x00000000006239c6 in sqlite3VtabSavepoint (db=0x9bf4a8, op=0,
iSavepoint=0) at sqlite3.c:100182
#4 0x00000000005e9f08 in sqlite3VdbeExec (p=0x9b9ac8) at sqlite3.c:66431
#5 0x00000000005e40d9 in sqlite3Step (p=0x9b9ac8) at sqlite3.c:61954
#6 0x00000000005e42ba in sqlite3_step (pStmt=0x9b9ac8) at sqlite3.c:62027
Thanks for reporting this.
Found one problem:
Ticket: http://www.sqlite.org/src/info/48f299634a
Fix: http://www.sqlite.org/src/info/3565fcf898
Please follow up if you try this fix and you still get
the crash.
Dan.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users