On Aug 11, 2009, at 4:28 PM, Mark Richards wrote: > D. Richard Hipp , On 8/11/2009 16:02: >> >> Perhaps pthreads is going goofy. Please recompile with - >> DSQLITE_THREADSAFE=0 and see if that helps. >> > BINGO. > > env CC="gcc-cris -mlinux -isystem $EROOT/include" CPP="gcc-cris > -mlinux -E -isystem $EROOT/include" CXX="g++-cris -mlinux -xc++ > -isystem $EROOT/include" LDFLAGS="-L$EROOT/lib" > OBJCOPY="objcopy-cris" LD="ld-cris -mcrislinux" AR="ar-cris" > RANLIB="ranlib-cris" NM="nm-cris" STRIP="strip-cris" ./configure > --host=cris-axis-linux-gnu > --prefix=/AEMDEV/83+/devboard-R2_10/target/cris-axis-linux-gnu > --enable-static=yes --enable-shared=yes --disable-threadsafe -- > disable-tcl > > > Works like a charm. > > How can I help find the issue with my test case?
On linux, SQLite has to start a thread in order to figure out if the program is using LinuxThreads or NPTL for its threading. (SQLite has to know which is used because there are serious bugs in LinuxThreads that SQLite has to work around.) So pthreads gets used once, by SQLite, even if you don't do any threading in your application. Probably something about that pthread_create() call is messing up the exec. If you app does not use threads, then by all means compile with SQLITE_THREADSAFE=0 because that makes SQLite run faster. > > /m > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
