summaryrefslogtreecommitdiffstats
path: root/tools/valgrind.supp
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@nvidia.com>2021-04-14 16:56:34 +0200
committerDonald Sharp <sharpd@nvidia.com>2021-05-05 16:52:51 +0200
commit56b99116f2082df6c9927f49b660295c69f1c7f8 (patch)
tree45acfc3fba505f6ccf3303d3f2de2c7f340d5625 /tools/valgrind.supp
parentMerge pull request #8619 from donaldsharp/sharp_redistribute (diff)
downloadfrr-56b99116f2082df6c9927f49b660295c69f1c7f8.tar.xz
frr-56b99116f2082df6c9927f49b660295c69f1c7f8.zip
tools: Add some more data to ignore for valgrind
When running valgrind there are some possible memory leaks. These memory leaks we have absolutely no control over, mark them as not worthy of being reported. Finally move the valgrind suppressions file from bgpd/ to tools/ this is because this suppressions file can be used beyond bgpd Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'tools/valgrind.supp')
-rw-r--r--tools/valgrind.supp32
1 files changed, 32 insertions, 0 deletions
diff --git a/tools/valgrind.supp b/tools/valgrind.supp
new file mode 100644
index 000000000..fbfb640b2
--- /dev/null
+++ b/tools/valgrind.supp
@@ -0,0 +1,32 @@
+{
+ <zlog_keep_working_at_exit>
+ Memcheck:Leak
+ match-leak-kinds: reachable
+ fun:calloc
+ fun:qcalloc
+ fun:zlog_target_clone
+}
+{
+ <libyang1_1.0.184>
+ Memcheck:Leak
+ match-leak-kinds: reachable
+ fun:calloc
+ fun:_dlerror_run
+ fun:dlopen@@GLIBC_2.2.5
+ obj:/usr/lib/x86_64-linux-gnu/libyang.so.1.9.2
+ fun:ly_load_plugins
+}
+{
+ <zprivs_init leak in a function we do not control>
+ Memcheck:Leak
+ fun:calloc
+ fun:cap_init
+ fun:zprivs_caps_init
+}
+{
+ <sqlite3 leak in a function we do not control>
+ Memcheck:Leak
+ fun:malloc
+ ...
+ fun:sqlite3_step
+}