Re: [gnome-db] Latest libgda breaks anjuta





2009/1/19 Johannes Schmid <jhs jsschmid de>
Hi!

I get the following backtrace with trunk while things work with 3.99.8:

#0  0x00007fa565c12c60 in write32bits (fd=0x7fa54c005d10,
   offset=<value optimized out>, val=<value optimized out>) at
sqlite3.c:12576
#1  0x00007fa565c34ba1 in subjournalPage (pPg=0x7fa54c82c340)
   at sqlite3.c:33450
#2  0x00007fa565c35048 in pager_write (pPg=0x7fa54c82c340) at
sqlite3.c:34311
#3  0x00007fa565c36baa in sqlite3PagerWrite (pDbPage=0x7fa54c82c340)
   at sqlite3.c:34420
#4  0x00007fa565c41ed0 in sqlite3BtreeDelete (pCur=0x7fa54c82bca8)
   at sqlite3.c:42224
#5  0x00007fa565c65d5d in sqlite3VdbeExec (p=0x7fa54c82a778) at
sqlite3.c:52850
#6  0x00007fa565c53fd8 in sqlite3_step (pStmt=0x7fa54c82a778)
   at sqlite3.c:47849
#7  0x00007fa565c09140 in gda_sqlite_provider_statement_execute (
   provider=<value optimized out>, cnc=0x4eee320, stmt=0x7fa54c826820,
   params=0x7fa54c32b080,
model_usage=GDA_STATEMENT_MODEL_RANDOM_ACCESS,
   col_types=0x7fa54c822010, last_inserted_row=0x0, task_id=0x0,
async_cb=0,
   cb_data=0x0, error=0x0) at gda-sqlite-provider.c:2571
#8  0x00007fa565b8c2b6 in gda_connection_statement_execute_v
(cnc=0x4eee320,
   stmt=0x7fa54c826820, params=0x7fa54c32b080,
   model_usage=GDA_STATEMENT_MODEL_RANDOM_ACCESS,
last_inserted_row=0x0,
   error=0x0) at gda-connection.c:1494
#9  0x00007fa565b93654 in gda_connection_statement_execute_non_select (
   cnc=0x4eee320, stmt=<value optimized out>, params=0x7fa54c32b080,

Yes, Massimo has already reported that problem, see bug #568093. As I don't have the time to investigate now, I'll revert the next version to SQLite 3.6.7 which worked correctly (Libgda does not use any feature specific to SQLite 3.6.10 yet).

The problem is I'd prefer to have a standalone program to reproduce the bug so it's easier to debug and if necessary it's easier to report to the SQLite people.

Vivien




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]