looks like a race condition! but it could also be uninitialized variable, but this is rarer these day as most compiler flag uninitialized var. unless your uninitialized var happen to be in a struct, this is why constructor are so important for struct/class
2017-02-27 11:28 GMT-05:00 Jeff Archer <jeffarch...@gmail.com>: > Hi All, > Any thoughts on this will be greatly appreciated. > > I am having an issue only on a specific tablet when it is running Android > 4.2.2. When Android is upgraded to 4.4.2 problems appears to be gone. I > still want to understand root cause to know if problem is really gone. > > My environment is a little unusual. I am running SQLite amalgamation > wrapped by JDBC driver. I was running 3.13.0 when issue was initially > found but have updated to 3.17.0 and no change. > > Problem always occurs while doing same operation but unable to predict when > it will occur. Problem occurs while reading in a specific table and a call > to sqlite3_column_text16() results in the following error being logged: > A/libc(5225): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=128), thread > 5225 (saltillo.chatpc) > and of course kills the process. > > Also, I find that attaching a debugger or writing too many log messages > seems to make the problems disappear also. > > Thanks, > Jeff > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Daniel *L'action accède à la perfection quand, bien que vivant, vous êtes déjà mort* *Bunan* _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
