On 9/21/15, Hugues Bruant <hugues at aerofs.com> wrote: > On Mon, Sep 21, 2015 at 8:43 PM, Richard Hipp <drh at sqlite.org> wrote: > >> On 9/21/15, Hugues Bruant <hugues at aerofs.com> wrote: >> > >> > I would be happy to build and test a patched sqlite with extra logging, >> > some sort of vdbe execution tracing >> >> Compile with -DSQLITE_DEBUG and then use "PRAGMA vdbe_debug=ON;" >> before the offending UPDATE and turn if off afterwards. >> > Will do. Does that go through the error/logging callback ( > https://www.sqlite.org/errlog.html) or directly to stdout/stderr?
Directly to stdout. If you can capture a malfunctioning trace, and send in the database file and the SQL statement that is running, that should allow us to localize the problem. -- D. Richard Hipp drh at sqlite.org