-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/12/12 14:43, Paul Menzel wrote: > The following code caused the segmentation fault.
By far the most likely cause is some other library or the app itself stomping on SQLite's memory. SQLite is on every Android device, every iOS device, virtually every browser (including Firefox and Chrome), used as a component in a lot of programs etc. All of that provides an immense amount of real world testing. Then add in the testing SQLite itself undergoes which is *far* in advance of most other software short of some safety critical systems. http://www.sqlite.org/testing.html All of the above is why it requires strong evidence in order to point the finger at SQLite. If you do want to trace this further then I recommend you try the valgrind program. However it does require some understanding of how memory is used and managed in a C based process. Also if glib/evolution/libcamel play silly games with memory (eg using their own allocators and pools) then it will completely obscure what is going on from valgrind. You'll most likely get better insight in a group devoted to evolution. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlC+j8YACgkQmOOfHg372QTexgCgldd0k9006XRiaetrEOcidSJ1 UMgAnjXoiTHUDa/oTxvXTkoPCg37DUmQ =uLKA -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
