On Aug 11, 2009, at 2:53 PM, Mark Richards wrote: > > When sqlite3_open() is called as above, got returns -1 (forever). -1 > returning from a NONBLOCK read is accepted behaviour, but pretty > quickly > the read() should give some data. Instead it returns -1 each time. > (If > I allow fd[0] to be in blocking mode, the read() never returns). > > Thinking that perhaps the > > A mangled stdout came to mind, but this does not appear to be the > case. > But maybe sqlite_open() or other internals diddle with stdout?
SQLite shouldn't be messing with stdin or stdout. We've done things like this before. We know it works. Perhaps pthreads is going goofy. Please recompile with - DSQLITE_THREADSAFE=0 and see if that helps. D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
