On Sep 10, 2008, at 10:09 AM, jerry wrote: > I recently upgraded to latest sqlite 3.6.2 and valgrind shows possible > memory loss of 272 bytes. I narrowed it down to a 2 line program of > just sqlite3_open and sqlite_close. Valgrind doc says that this is > probably a memory leak unless you are doing funny things with > pointers. > I saw the early message suggesting sqlite3_shutdown but that had no > effect. Is this a bug or is there some option I should be using to > prevent this? >
It appears that the pthreads library does a couple of allocations to create some thread-local storage. This is pthreads thing. There is nothing SQLite can do about it. If you are concerned, compile with - DSQLITE_THREADSAFE=0. This is not a bug in SQLite. D. Richard Hipp [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
