Repository navigation
Expand file tree
/
Copy pathvalgrind.suppress
More file actions
42 lines (40 loc) · 1.59 KB
/
Copy pathvalgrind.suppress
File metadata and controls
42 lines (40 loc) · 1.59 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
# nginx allocates two things once and lets the process exit take them back,
# so valgrind calls them lost. Neither comes from this module: both traces
# end in nginx's own code, and the module does not appear in either.
#
# These two are the only entries, and that is measured, not assumed. With
# an empty file the suite reports exactly these and nothing else -- no
# invalid read, no uninitialised value, no conditional jump. Anything that
# was in here beyond them suppressed something that never happens.
#
# Two things read this file: Test::Nginx, which looks for it by that name in
# the directory the suite runs from, and the valgrind workflow, which hands
# it to the wrapped driver with --suppressions. One file for both, because
# a second copy is a second thing to keep right.
#
# Note which cycle function they come through: Test::Nginx runs nginx with
# master_process off, so everything here is the single-process path. An
# entry for the master's own path would never be reached from this suite
# and so would be an entry nobody can check.
#
# If a later nginx brings a finding back, valgrind will say so with a full
# trace. Add it then, with a name and a reason, rather than keeping one
# here on the chance that it is still needed.
{
nginx keeps the environment array until the process ends
Memcheck:Leak
match-leak-kinds: definite
fun:malloc
fun:ngx_alloc
fun:ngx_set_environment
...
}
{
nginx keeps the connection and event arrays until the process ends
Memcheck:Leak
match-leak-kinds: definite,indirect
fun:malloc
fun:ngx_alloc
fun:ngx_event_process_init
...
}