We observe very similar problem.
#1 0x087ec9f7 in sqlite3VXPrintf ()
#2 0x087f816d in sqlite3MPrintf ()
#3 0x088781e5 in sqlite3VtabFinishParse ()
#4 0x0885190f in yy_reduce ()
#5 0x0884d4d8 in sqlite3Parser ()
#6 0x087fc0ce in sqlite3RunParser ()
#7 0x088aa396 in sqlite3Prepare ()
#8 0x087fae18 in sqlite3LockAndPrepare ()
#9 0x087f9a88 in sqlite3_exec ()
#10 0x086588a7 in sqlite::StorageBase::exec_query (this=0x2c2a47c0,
query=0x2c7fffc0 "CREATE VIRTUAL TABLE temp.vtb_wayxzmbo USING
vtable_module_344", quiet=false) at SqliteStorageBase.cpp:286
It always crashes when "CREATE VIRTUAL TABLE ..." is being executed, always
with the same backtrace.
I spent many days reviewing and testing my code to eliminate possible cause but
so far I see nothing wrong with it.
Probability of this crash is so very low so that problem can be reproduced only
on hi loaded production servers.
(Where such virtual tables are created and dropped millions of times during a
day)
I am going to compile sqlite without optimizations and with debug symbols and
wait for a crash
to try and track the root of the problem from within sqlite.
Though I doubt very much this is sqlite problem at all and not an incorrect
vtable implementation on my side.
SQLite version 3.8.6 2014-08-15 11:46:33
> We are compiling the 3.8.7.1 using clang arm64 for iOS. Following set:
>
> #define SQLITE_ENABLE_COLUMN_METADATA 1
> #define HAVE_INTTYPES_H 1
> #define HAVE_STDINT_H 1
> #define HAVE_USLEEP 1
>
> #define SQLITE_DEBUG 1
> #define SQLITE_MEMDEBUG 1
>
> WAL mode.
>
> In MallowRaw(), very rarely, seeing the lookaside buffer pBuf or pBuf->next
> getting corrupted with ASCII from our CREATE TABLE statements. ('INTEGER' or
> part of one of our field names). Thing is, we are not running the schema
> create code on these runs (the DB already exists), so these strings must be
> coming from sqlite_master, AFAIKT.
>
> None of the SQLITE_DEBUG or SQLITE_MEMDEBUG asserts fire. When it happens, it
> happens early in the application run.
>
> Hard to set a hardware write breakpoint on such a mutable thing.
>
> I fully believe the problem is of my own creation, but interested in any
> thoughts or if anyone has seen anything like this.
>
> Thanks, as always,
>
> -- Ward
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
