On Tue, 1 Jul 2014 08:07:52 +0300 Mattan Shalev <mat...@reduxio.com> wrote:
> Hey guys, > I'm getting signal 6 during sqlite_step in WAL mode. Working on Ubuntu > 12.04, sqlite3 3.7.9. > One process is the writing continuously, while other process reads > from the DB in a multi threaded access. I made sure that sqlite is > configured to serialised mode. > > Here is the backtrace: > > #0 0x00007f4f78f0d08d in nanosleep () > #from /lib/x86_64-linux-gnu/libc.so.6 1 0x00007f4f78f0cf2c in sleep > #() from /lib/x86_64-linux-gnu/libc.so.6 2 0x00007f4f7982d881 in > #signal_catch (signo=6) at signal_masker.c:35 3 <signal handler > #called> 4 0x00007f4f78e83425 in raise () > #called> from /lib/x86_64-linux-gnu/libc.so.6 > #5 0x00007f4f78e86b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 > #6 0x00007f4f78ec139e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > #7 0x00007f4f78ecbb96 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > #8 0x00007f4f77661690 in sqlite3_free () from > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > #9 0x00007f4f77664b96 in ?? () from > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > #10 0x00007f4f77664c7c in ?? () from > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > #11 0x00007f4f77664cb0 in ?? () from > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > #12 0x00007f4f7768b477 in ?? () from > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > #13 0x00007f4f7769a249 in ?? () from > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > #14 0x00007f4f776a9689 in ?? () from > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > #15 0x00007f4f776ae451 in sqlite3_step () from > /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > #16 0x00007f4f79416557 in get_down_intervals_size > #(start_time=1403711040, > end_time=1577836800, > size=0x7f3c49c68958) at stats_ext.c:202 > #17 0x0000000000407f80 in ns__get_stats_performance (s=0x1e4cb00, > start_time=1403711040, end_time=1577836800, > time_unit=NS_MINUTES, resource_id=0, ret=0x7f3c49c68990) at > msg_handlers/capi_wrappers.c:636 > #18 0x00000000004461c1 in soap_serve_ns__get_stats_performance > (soap=0x1e4cb00) at soapServer.c:1294 > #19 0x00000000004415ae in soap_serve_request (soap=0x1e4cb00) at > soapServer.c:119 > #20 0x0000000000440f3e in soap_serve (soap=0x1e4cb00) at > #soapServer.c:39 21 0x0000000000403c90 in process_request > #(s=0x1e4cb00) at be_server.c:111 22 0x00007f4f79a3de9a in > #start_thread () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #23 0x00007f4f78f413fd in clone () > #from /lib/x86_64-linux-gnu/libc.so.6 24 0x0000000000000000 in ?? () > > Does anyone has an idea? Don't know with the information you show. But I suggest you to not use sqlite3.so from system and add sqlite3.c and sqlite3.h to your project. Therefore you can, among other improvements, build a newer and more error free sqlite3 version with debug information on and see what happens between the #8 sqlite3_free() call and #14 sqlite3_step(). Increase in compile time is minimal (less than 2 seconds) in my laptop in a fresh rebuild. > > Thanks! > > Mattan. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users --- --- Eduardo Morras <emorr...@yahoo.es> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
