Actions
Fix #11247
closedvalgrind: do not warn on lttng cleanup issues
% Done:
0%
Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
The relevant bits:
<kind>Leak_StillReachable</kind> <xwhat> <text>32 bytes in 1 blocks are still reachable in loss record 41 of 281</text> <leakedbytes>32</leakedbytes> <leakedblocks>1</leakedblocks> </xwhat> <stack> <frame> <ip>0x4C2CC70</ip> <obj>/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so</obj> <fn>calloc</fn> </frame> <frame> <ip>0x6E5F68F</ip> <obj>/lib/x86_64-linux-gnu/libdl-2.19.so</obj> <fn>_dlerror_run</fn> <dir>/build/buildd/eglibc-2.19/dlfcn</dir> <file>dlerror.c</file> <line>141</line> </frame> <frame> <ip>0x6E5F0C0</ip> <obj>/lib/x86_64-linux-gnu/libdl-2.19.so</obj> <fn>dlopen@@GLIBC_2.2.5</fn> <dir>/build/buildd/eglibc-2.19/dlfcn</dir> <file>dlopen.c</file> <line>87</line> </frame> <frame> <ip>0x507D30F</ip> <obj>/usr/lib/x86_64-linux-gnu/liblttng-ust.so.0.0.0</obj> </frame> <frame> <ip>0x5091958</ip> <obj>/usr/lib/x86_64-linux-gnu/liblttng-ust.so.0.0.0</obj> <fn>lttng_ust_baddr_statedump_init</fn> </frame> <frame> <ip>0x507C894</ip> <obj>/usr/lib/x86_64-linux-gnu/liblttng-ust.so.0.0.0</obj> <fn>lttng_ust_init</fn> </frame> <frame> <ip>0x4010139</ip> <obj>/lib/x86_64-linux-gnu/ld-2.19.so</obj> <fn>call_init.part.0</fn> <dir>/build/buildd/eglibc-2.19/elf</dir> <file>dl-init.c</file> <line>78</line> </frame> <frame> <ip>0x4010222</ip> <obj>/lib/x86_64-linux-gnu/ld-2.19.so</obj> <fn>_dl_init</fn> <dir>/build/buildd/eglibc-2.19/elf</dir> <file>dl-init.c</file> <line>36</line> </frame> <frame> <ip>0x4001309</ip> <obj>/lib/x86_64-linux-gnu/ld-2.19.so</obj>
Introduced at merge commit dca722ec7b2a7fc9214844ec92310074b5cb2faa.
We just want to ignore the warning.
Actions