On 14 Jun 2015, at 5:39pm, Mel Llaguno <mllaguno at coverity.com> wrote:
> We have an application with embedded SQLite 3.6.14.2 which is being accessed > by multiple processes. These processes connect to the database with a BEGIN > IMMEDIATE TRANSACTION. Under what circumstances, if any, can database > corruption actually occur (ruling out filesystem instability and power > loss/kernel panics)? Can I ask you to read this page <https://www.sqlite.org/howtocorrupt.html> and then post again with your guesses as to which section(s) might be relevant ? As general advice, check the result codes from all SQLite calls, even if there's nothing you can do when they go wrong (e.g. sqlite_close()). Often the first indication that you're overwriting SQLite memory is something weird like _finalize() returning something other than SQLITE_OK. Simon.
