On 20.12.2010 13:32 Simon Slavin said the following: > > On 20 Dec 2010, at 12:17pm, Michael Steiger wrote: > >> In the meantime I further analyzed the problem and I also looked at the >> corrupt databasefile. To my surprise it contained some logfile output >> from another library I am using. It seems that if I turn on logging for >> this library some log output is written to the database file. But I have >> absolutely no idea how this mixup can happen. > > Since SQLite does not do any logging, it would seem that the problem is not > entirely within the SQLite library. Since you appear to be using plain C > function calls to access SQLite this suggests that there is some sort of > problem with your memory handling. I am sure that the problem is not entirely within SQLite. Yes, I am using plain C and it must be some memory error. Just need to find it ;-)
> Is there a chance that you are using either the file handle or the > database handle for something other than SQLite3 calls ? And I have already scanned my code if there is a mixup of the database handle and some other code. But I found none. "Using the file handle"? I only open the database using sqlite3_open and then use the database handle returned. No direct file access to the SQLite databasefile. > Can you tell us what is producing that log text you found ? I am developing network appliances using EZchip network processors and for implementing some backend code I recently switched to SQLite. The code which produces the log text is not called from my code but is used deep inside this library (I have the source code to look at). Thanks Michael _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users