-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/20/2010 05:55 PM, Sam Carleton wrote: > Ok, that is what i am doing, checking the value of db and closing if > it has a value. So why might closing the db cause a crash?
It is 99 point lots of nines percent certain that you have a programming error related to memory such as using freed memory or objects, doubly freeing etc. If you have access to Linux then a quick run with Valgrind will give the answer. If you are stuck with Windows then you are best off using some sort of memory debugging tool although ones that only detect leaks are likely to be almost useless. It will likely also help to compile sqlite with -DSQLITE_DEBUG which will cause lots more assertion checks in SQLite and hence more likely to catch things earlier. If it is non-SQLite using code that is buggy then you really need to find that code. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkweyNYACgkQmOOfHg372QQjhgCgx1IjrSDMZYefhrGMAE766YU4 tcgAniTAZjVYQ7fjU1KO5TOXg8kvqTbN =dR5T -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
