On Fri, Apr 15, 2011 at 01:20:11PM +0700, Dan Kennedy wrote:
> Can you post the stack-trace from the core file? With debugging
> symbols if possible.
Sorry, the backtrace is unusable:
(gdb) bt
#0 __nanosleep50 (rqtp=0x7f7fffffc1b0, rmtp=0x0)
at /archive/cvs/src/lib/libpthread/pthread_cancelstub.c:389
#1 0x00007f7ff7708008 in ?? ()
#2 0x00000000000001a4 in ?? ()
#3 0x0000000000000202 in ?? ()
#4 0x0000000000000000 in ?? ()
Is there a way to get more useful output from the sqlite3 executable
(that hangs?)?
> > Perhaps non-standard options used during compilation are
> > -DUSE_PREAD
> > -DSQLITE_ENABLE_UNLOCK_NOTIFY=1
>
> Could easily be the ENABLE_UNLOCK_NOTIFY.
I disabled both of these options but still see the problem.
Thomas
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
