Chris Brown wrote: >>The "fossil" configuration management system (used to control the >>documentation of SQLite - see http://www.fossil-scm.org/ for details >>and http://www.sqlite.org/docsrc/timeline for an example) calls >>system() after sqlite3_open() in multiple places and it works just >>fine on Linux, OSX, various other flavors of unix, and even win32. >>Are you sure that SQLite is to blame here? > > > No I couldn't be 100% certain that SQLite is to blame but I have stripped > out all other code to do the following and it hangs on the second system > call: > > system("whoami"); > sqlite3_open("/bin/test/testdb", &db); > sqlite3_close(db); > system("whoami"); > > I have checked the return value of sqlite3_open and it is zero. If I remove > the calls to sqlite3_open and sqlite3_close then both system calls complete > correctly. > > I also tried Peter's suggestion but that didn't have any affect either. > > Chris > Are you closing standard output or standard input?
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
