Joe,
> It's worked on every device that I've used in the past.
I hope you see the funny side when I say, this doesn't fill me with a great
amount of confidence as according to your previous messages you don't have a
device to test on, only emulators. :)
> I have no idea what the "rtlogshimeng" DLL is. I tried searching for
> references to it on the web to no avail. It might be totally harmless;
> however, it seems to be implicated by the debug output.
I have no doubt that the dll is harmless as even with a complete reflash of the
device it exists. My guess would be that it is a Motorola device-specific
library since we cannot find any reference to it and given your comment above
(despite my tongue in cheek response.)
Still the fact that the problem occurs between another threads
sqlite3_finalize() calls and that calling GC.Collect before making a database
connection seems to hide the issue doesn't suggest that SQLite is completely
exonerated.
> Does everything work properly when only a single thread is used?The answer
> is, no if the only thread doing the database accessing is not the foreground
> (UI) thread. If you mean, there is literally just a UI thread making
> database connections in amongst user activity, then (I need to do more
> testing but) certainly the issue becomes a lot less easy to recreate (i.e. in
> the small amount of time I've had to test it has not reoccured in those
> conditions). Unfortunately the app I had in mind requires more than a single
> thread even if only one thread can access the database at once.
Please do not interpret my disappointment as criticism, it is more of a
compliment to SQLite that I am so frustrated that I will not be able to take
advantage of it.
Thank you again for all your help, it was and is greatly appreciated. At least
now I know.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
