1 # Valgrind suppressions for stuff that we cannot control
3 # Memory leaks in standard tools (e.g. dash, tail, or sort)
5 Memory leak in /bin tools
12 Memory leak in /usr/bin tools
18 # There's a constant leak of 56 bytes in the depths of libc which
19 # manifests, for example, when using backtrace()
21 Memory leak in libc/dlopen with -pthread
24 fun:_dl_map_object_deps
31 fun:__libc_dlopen_mode
34 # Another problem in glibc, where makecontext does not reset the EBP register,
35 # and backtrace goes too far when walking up the stack frames
37 Invalid read in backtrace, called after makecontext
44 #There seems to be an issue with libc using an uninitialized value somewhere in dlopen
46 Invalid read in dl_start
49 fun:expand_dynamic_string_token
54 # 72704 bytes leak from GCC >5.1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64535
56 Memory leak in dl_init
58 match-leak-kinds:reachable
60 obj:/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21
65 # Memory leaks appearing to be in libcgraph. They can be seen with the
66 # following simple program:
68 # | #include <stdio.h>
69 # | #include <graphviz/cgraph.h>
70 # | int main(int argc, char *argv[])
73 # | printf("Usage: %s <dotfile>\n", argv[0]);
77 # | FILE *inf = fopen(argv[1], "r");
78 # | g = agread(inf, 0);
85 Memory leak in libcgraph (1/2)
89 obj:/usr/lib/libcgraph.so*
95 Memory leak in libcgraph (2/2)
100 obj:/usr/lib/libcgraph.so*
105 # We're not interested by memory leaks in the Lua interpreter