There appears to be a problem in the FTS3 module relating to tokenizers. In my case if I register a custom tokenizer on a database connection that does not have a table using the custom tokenizer, then when I run my program with Valgrind I get a lot of "Use of uninitialised value of size 4" messages. The messages occur when a prepared statement is stepped.
If I use the same custom tokenizer on a different database connection that does have a table using the custom tokenizer, all of these Valgrind messages go away. Has anyone else come across this? In my use it is not toxic, but it just seems odd, which is why I am mentioning it. I've included one of the Valgrind message traces. ==4900== Use of uninitialised value of size 4 ==4900== at 0x45C7416: fts3FindElementByHash (sqlite3.c:103485) ==4900== by 0x45DA08D: sqlite3Fts3HashInsert (sqlite3.c:103596) ==4900== by 0x45DA494: fts3PendingTermsAdd (sqlite3.c:105513) ==4900== by 0x46182FD: fts3UpdateMethod (sqlite3.c:105574) ==4900== by 0x462A3CB: sqlite3VdbeExec (sqlite3.c:58974) ==4900== by 0x4612BCF: sqlite3_step (sqlite3.c:51732) ==4900== by 0x461C489: sqlite3_exec (sqlite3.c:76845) ==4900== by 0x80EF672: db_run_query_on_con (db_util.c:304) ==4900== by 0x80E8933: db_load_songs (db_manage.c:1970) ==4900== by 0x80E8423: db_load_device (db_manage.c:1798) ==4900== by 0x80E2699: db_check_msg_que (db_main.c:251) ==4900== by 0x80E23B4: db_task_main (db_main.c:148) ==4900== by 0x440880D: start_thread (pthread_create.c:300) ==4900== by 0x48BBA0D: clone (clone.S:130) Travis Orr IVL Audio Inc #3-6703 Rajpur Place Victoria BC V8M 1Z5 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
