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?
==9078== Memcheck, a memory error detector. ==9078== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al. ==9078== Using LibVEX rev 1575, a library for dynamic binary translation. ==9078== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP. ==9078== Using valgrind-3.1.1, a dynamic binary instrumentation framework. ==9078== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al. ==9078== For more details, rerun with: -v ==9078== ==9078== ==9078== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 15 from 1) ==9078== malloc/free: in use at exit: 272 bytes in 2 blocks. ==9078== malloc/free: 29 allocs, 27 frees, 57,720 bytes allocated. ==9078== For counts of detected errors, rerun with: -v ==9078== searching for pointers to 2 not-freed blocks. ==9078== checked 22,668,420 bytes. ==9078== ==9078== LEAK SUMMARY: ==9078== definitely lost: 0 bytes in 0 blocks. ==9078== possibly lost: 272 bytes in 2 blocks. ==9078== still reachable: 0 bytes in 0 blocks. ==9078== suppressed: 0 bytes in 0 blocks. ==9078== Reachable blocks (those to which a pointer was found) are not shown. ==9078== To see them, rerun with: --show-reachable=yes _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
