D. Richard Hipp , On 8/11/2009 16:39: > 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. > Would it help to know, where threading is enabled in the library, if pthread_create() fails? Is there a function that can tell me the status?
Or, is there a switch that will force sqlite to use native thread library instead? Fortunately my app isn't forking out SqLite tasks. It does fork itself to run as a daemon, tho. All my tests were done *before *forking. I tried the same test cases after the fork and got the same results. /m _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
