-
Notifications
You must be signed in to change notification settings - Fork 723
Expand file tree
/
Copy pathvalgrind.supp
More file actions
72 lines (66 loc) · 1.68 KB
/
Copy pathvalgrind.supp
File metadata and controls
72 lines (66 loc) · 1.68 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
# SPDX-License-Identifier: GPL-2.0-only
#
# Valgrind suppressions for known false positives in the nvme-cli test suite.
#
# Used automatically by: meson test --setup valgrind
#
# Three categories of suppressions are defined here:
#
# 1. Bash interpreter internals — the valgrind exe_wrapper invokes bash
# directly for shell-script-based tests. Leaks from bash itself are
# not our code.
#
# 2. CPython interpreter internals — Python test scripts import our libnvme
# Python bindings. CPython's import machinery, marshal, and unicode
# internals generate reports that are not leaks in our code.
# Two obj: patterns are needed: one for distros where Python is a static
# binary (/usr/bin/python3.*) and one for distros where it is dynamically
# linked against a shared library (*libpython3*).
#
# 3. SWIG module teardown — SWIG allocates a varlink object during module
# initialisation that CPython never releases during interpreter shutdown.
# This is a known SWIG limitation, not a leak in libnvme.
{
bash-interpreter-leak
Memcheck:Leak
match-leak-kinds: all
...
obj:*/bash
}
{
cpython-interpreter-leak
Memcheck:Leak
match-leak-kinds: all
...
obj:*/python3*
}
{
cpython-shared-library-leak
Memcheck:Leak
match-leak-kinds: all
...
obj:*libpython3*
}
{
cpython-interpreter-cond
Memcheck:Cond
...
obj:*/python3*
}
{
cpython-shared-library-cond
Memcheck:Cond
...
obj:*libpython3*
}
{
swig-python-module-teardown
Memcheck:Leak
match-leak-kinds: definite
fun:malloc
fun:_PyObject_New
fun:SWIG_Python_newvarlink
fun:SWIG_globals
fun:SWIG_Python_DestroyModule
...
}