On Thu, Jun 17, 2010 at 02:07:50PM -0700, VIKRANT scratched on the wall: > I have following C program > It takes the DB path as argument > > For testing, I have placed the DB on a dir over the NFS > > Now after the open call, I unshare the NFS from the NFS > server to generate I/O errors > Once the exec starts receiving errors, it is leaking memory.. > after 6 hours, its leaking upto 1G
"It" is not leaking memory, you are: http://sqlite.org/c3ref/exec.html If the 5th parameter to sqlite3_exec() is not NULL then any error message is written into memory obtained from sqlite3_malloc() and passed back through the 5th parameter. To avoid memory leaks, the application should invoke sqlite3_free() on error message strings returned through the 5th parameter of of sqlite3_exec() after the error message string is no longer needed. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
