On Tue, May 10, 2011 at 2:17 PM, Ian Hardingham <i...@omroth.com> wrote:
> I'm sure that this is to do with the way I am using SQLite. I do not > have time to radically change my methodology at this point, but I do > need to fix a rather severe memory leak I'm having. > > i don't see any immediate leaks in what you posted, but what you posted relies on tons of code we can't see. Pointer-managing classes like VectorPtr<T*> can certainly be a source of leaks. i highly recommend running your program through valgrind and see what it says - it will point you directly to the source of the leak. Valgrind can be used like this: valgrind --leak-check=full -v --show-reachable=yes --track-origins=yes ./MyProgram -- ----- stephan beal http://wanderinghorse.net/home/stephan/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
