On Tue, Jan 7, 2014 at 3:55 PM, Sascha Sertel <sascha.ser...@gmail.com>wrote:

> Hello,
>
>
> I'm hoping someone has any ideas what to do about the error messages I'm
> getting from SQLite 3.8.1 when run on Android:
>
>
> Getting warning: "cannot fstat db file  "
>
> -- please take note that there is a blank inserted for the file name
>
>
> This is on Android 4.3 KitKat with manually compiled (not built-in one)
> SQLite 3.8.1 (from amalgamation) using PERSIST journaling when writing to
> db from multiple threads (serialized with mutex) in explicit transaction
> context.
>
>
> The same transactions are working fine on SQLite 3.7.16 but I would like to
> upgrade to 3.8.x. and solve these issues.
>

Probably it is "working fine" in 3.8.x too.  The warning has been added.
But it is just a warning, not an error.

The code to implement the warning is here:

    http://www.sqlite.org/src/artifact/abeb9d54036aaea6?ln=1351-1356

Can you run your application in a debugger, or maybe add some "printf()s"
to the code to try to figure out why the call to fstat() is failing?  At
the very least, get us a call-stack for when the failure occurs?



>
>
> Any ideas or suggestions are much appreciated!
>
>
> // Sascha
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to