Our sqlite version is "SQLite version 3.8.8.1".
Modify a configuration data while reading a big configuration DB(show 
configuration).  It goes to busyhandler and write is successful and read 
configuration codes goes to core dump. Is there any idea why going to core 
dump?  Is something to do with mutex handling? Thanks.

ChingChang

int32
DbHandle::registerBusyHook( sqlite3* db, dbCallback_data_t *cbData ) {
  sqlite3_busy_handler( db,
                                                &dbBusyHandler,
                                                (void*)cbData );
  return 0;
}

(gdb) bt
#0  0x2ce4f4fc in sqlite3_step () from /ovn/lib/libsqlite3.so.3
#1  0x2ba471cc in SqlQuery::step(int) () from /ovn/lib/libplatform.so.1
#2  0x10189e50 in printServiceConfig(void*, ArgumentArray*, unsigned char, 
char*, void**, char*) ()
#3  0x1018a384 in IsgShowCfgSvc ()
#4  0x2bf2f3f8 in OvnRcRunShowConfig () from /ovn/lib/libEngine.so.1
#5  0x10129774 in IsgShowCfgMainConfig ()
#6  0x2bf2f3f8 in OvnRcRunShowConfig () from /ovn/lib/libEngine.so.1
#7  0x10122b04 in IsgShowCfg ()
#8  0x2bf2d200 in RcParseLine () from /ovn/lib/libEngine.so.1
#9  0x2bf28788 in RcFiniteStateMachine () from /ovn/lib/libEngine.so.1
#10 0x2bf22298 in AllegroMainTask () from /ovn/lib/libEngine.so.1
#11 0x2bf23b2c in c_main () from /ovn/lib/libEngine.so.1
#12 0x2bf31af0 in app_main(int, char**) () from /ovn/lib/libEngine.so.1
#13 0x1004c148 in main ()

_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to