On 12/27/19, Richard Hipp <d...@sqlite.org> wrote: > On 12/27/19, Richard Hipp <d...@sqlite.org> wrote: >> >> This is the third such false-positive bug like that this month.... > > And now there is a fourth: https://sqlite.org/src/info/5fbc159eeb092130c6f2
For those of you still keeping score... A fifth example of this is ticket https://www.sqlite.org/src/info/de4b04149b9fdeae The problem there was another false-positive in the OP_SCopy misuse detection mechanism. The fix was to improve that mechanism to avoid the false positive. But since the OP_SCopy misuse detection is a debugging feature that is only present in the code when it is compiled with SQLITE_DEBUG, the "fix" makes no changes to deliverable code. That is to say, the compiled machine code for the SQLite library is byte-for-byte identical before and after the fix. Even so, the OP_SCopy misuse detection logic is an important testing component of SQLite, and we sincerely appreciate bug reports against that feature. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users