durga.disc wrote: > We have an application on unix platform with sqlite database which > is running from last 2 years. pretty well. > > We recently ported on Windows too. Crashed at inserting record in a > small database(less than 20 records, record has 10 columns). It's not > reproducible. > > call stack: > > ntdll!RtlEnterCriticalSection+0x12 > !winMutexEnter+0x13 > !sqlite3_mutex_enter+0x19 > !sqlite3_step+0x5e > > Is it known issue with 3.7.11 on Windows. Any idea?
That call stack shows (attempted) execution of some code which is hit very frequently by most any Windows-hosted SQLite app. This fact, together with the extensive testing of SQLite on Windows, suggests that your problem lies within code you have not shown, and most likely within your own code. If it is not reproducible, it may prove worthwhile to eliminate threading issues, if you can, and to check for heap corruption and buffer over-writes. Going in, it is best to not read too much into your code running "pretty well" on a Unix platform. Have you run your code with Valgrind (or equivalent) on that platform? If not, doing so may help you uncover a bug which affects behavior more badly on Windows with your present build. On Windows, you can use debugging aids built into the debug version of the MS C runtime. (See http://msdn.microsoft.com/en-us/library/zh712wwf.aspx .) Quite unlikely is the prospect for somebody here to say "Yes, we routinely see crashes on Windows in the sqlite3_mutex_enter code." You are going to have to debug this. Good luck. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
