Guillaume Fougnies wrote:
CFLAGS : -O2 -ggdb -DTHREADSAFE=1 -DNDEBUG=0 \
-DOS_UNIX=1 -DOS_WIN=0 -DHAVE_USLEEP=1



For debugging, it is best, I think, to omit the -DNDEBUG altogether. Unless I'm badly mistaken, any definition of the NDEBUG macro will disable the assert()s, even a definition of "0".


1) Sometimes, i get this error with sqlite_exec char* err: "database schema has changed" without a usefull error returned by the method. I was hoping something like SQLITE_SCHEMA but i'm getting SQLITE_ERROR.

Probably the SQLITE_SCHEMA error is being incorrectly converted into an SQLITE_ERROR somewhere as the call stack unwinds. I'll fix it - but I consider this a minor problem. If you can give me more hints on how to reproduce it, that would be helpful.


2) Disk image corruption (with indexes):
After a time of running, i get this error in return:
"database disk image is malformed".
The time is quite short (few seconds) when i'm using the
default busy callback "sqliteDefaultBusyCallback" via
"sqlite_busy_timeout".
The time is short (env 30s) when i'm using a simple
busy callback like: { usleep( 100 ); return 1; }

This is very serious. If you are able to send me the code that generates this problem and tell me how to reproduce it, that would be very helpful. Let's focus on problem (2) for the time being and go back to problem (1) after (2) has been resolved.



--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to