summaryrefslogtreecommitdiffstats
path: root/tools/valgrind/memcheck/suppressions.txt
diff options
context:
space:
mode:
Diffstat (limited to 'tools/valgrind/memcheck/suppressions.txt')
-rw-r--r--tools/valgrind/memcheck/suppressions.txt11
1 files changed, 10 insertions, 1 deletions
diff --git a/tools/valgrind/memcheck/suppressions.txt b/tools/valgrind/memcheck/suppressions.txt
index d07edae..47cb05b 100644
--- a/tools/valgrind/memcheck/suppressions.txt
+++ b/tools/valgrind/memcheck/suppressions.txt
@@ -171,7 +171,16 @@
}
{
- # Strange...
+ # "The section of the SQLite library identified works exactly as it should."
+ # http://www.sqlite.org/cvstrac/tktview?tn=536,39
+ # http://www.sqlite.org/cvstrac/tktview?tn=694,39
+ # http://www.sqlite.org/cvstrac/tktview?tn=964,39
+ # This looks like a case where an entire page was allocated, the header and
+ # perhaps some data was written, but the entire buffer was not written to.
+ # The SQLite authors aren't very interested in adding code to clear buffers
+ # for no reason other than pleasing valgrind, but a patch might be accepted
+ # under a macro like SQLITE_SECURE_DELETE which could be construed to apply
+ # to cases like this. (Note that we compile with SQLITE_SECURE_DELETE.)
bug_20653a
Memcheck:Param
write(buf)