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
|
# Valgrind may generate false positives on pthreads: https://stackoverflow.com/a/13132968
# Without these suppressions, the following tests will fail:
# s2n_examples_test, s2n_fork_generation_number_test, s2n_init_test, s2n_key_update_threads_test, and s2n_random_test.
{
pthread_false_positive
Memcheck:Leak
match-leak-kinds: possible
fun:calloc
...
fun:allocate_dtv
fun:_dl_allocate_tls
fun:allocate_stack
fun:pthread_create@@*
...
fun:main
}
# This memory leak is believed to be caused by backtrace() loading libgcc dynamically.
# See https://man7.org/linux/man-pages/man3/backtrace_symbols_fd.3.html
# We were unable to find any relevant bug reports. However, testing showed that the memory
# leak didn't scale with the number of calls to backtrace(), both supporting this theory and
# limiting the potential impact of the leak.
{
stacktrace_suppression
Memcheck:Leak
match-leak-kinds: possible
fun:malloc
fun:malloc
fun:_dlfo_mappings_segment_allocate
fun:_dl_find_object_update_1
fun:_dl_find_object_update
fun:dl_open_worker_begin
fun:_dl_catch_exception
fun:dl_open_worker
fun:_dl_catch_exception
fun:_dl_open
fun:do_dlopen
fun:_dl_catch_exception
fun:_dl_catch_error
fun:dlerror_run
fun:__libc_dlopen_mode
fun:__libc_unwind_link_get
...
fun:backtrace
...
fun:main
}
# TODO: fix the pedantic leak errors from s2n_fork_generation_number_test
{
ignore_s2n_fork_generation_number_test
Memcheck:Leak
match-leak-kinds: reachable
...
fun:s2n_test_case_default_cb
fun:main
}
{
ignore_s2n_fork_generation_number_test
Memcheck:Leak
match-leak-kinds: reachable
...
fun:s2n_test_case_madv_wipeonfork_cb
fun:main
}
|
