Re: [sqlite] sqlite3_expanded_sql is reading freed heap memory

> On Feb 6, 2018, at 6:20 PM, Richard Hipp wrote: > > The line numbers in your ASAN output below seem incorrect. The > SHA3-256 hash for sqlite3.c version 3.22.0 should be > 206df47ebc49cd1710ac0dd716ce5de5854826536993f4feab7a49d136b85069. > What is the hash on the "sqlite3.c" file you are usi

Re: [sqlite] sqlite3_expanded_sql is reading freed heap memory

On 2/6/18, Jens Alfke wrote: > I've got a repeatable situation in my library's unit tests wherein the Clang > Address Sanitizer catches sqlite3_expanded_sql() reading from a freed heap > block. This is with SQLite 3.22 on MacOS 10.13.3. > > The background: I've added some code to my library to log

Re: [sqlite] sqlite3_expanded_sql is reading freed heap memory

can you use sqlite3_sql instead; it won't be complete information... but ya, the time that expanded_sql is valid is really only while the bound parameters are still valid. (could re-bind parameters when done I guess) On Tue, Feb 6, 2018 at 1:07 PM, Jens Alfke wrote: > I've got a repeatable

[sqlite] sqlite3_expanded_sql is reading freed heap memory

I've got a repeatable situation in my library's unit tests wherein the Clang Address Sanitizer catches sqlite3_expanded_sql() reading from a freed heap block. This is with SQLite 3.22 on MacOS 10.13.3. The background: I've added some code to my library to log warnings if the database is closed