https://bugs.kde.org/show_bug.cgi?id=515183
--- Comment #2 from daxin <[email protected]> --- (In reply to Paul Floyd from comment #1) > Stanza causing this > { > dtv-addr-init > Memcheck:Leak > match-leak-kinds: possible,reachable > ... > fun:allocate_dtv_entry > fun:allocate_and_init > fun:tls_get_addr_tail* > fun:__tls_get_addr > } > > Helgrind and DRD have quite a few suppressions that have ... in the first > line. > > Should we restrict --num-callers to at least 2? > > Leak suppression would only match the allocation function. That means that > either all allocations by malloc etc get suppressed or none. Referring to the logic in the commit https://github.com/LouisBrunner/valgrind-macos/commit/d74a2608e59d16033673ecdf85961ebe1db2e2da, does it retain the original fun:malloc line and then add new ... wildcards for multi-level malloc matching? Specifically, it is shown as follows: { dtv-addr-init Memcheck:Leak match-leak-kinds: possible,reachable fun:malloc ... fun:allocate_dtv_entry fun:allocate_and_init fun:tls_get_addr_tail* fun:__tls_get_addr } Following the above instructions, executing the command `valgrind --num-callers=1 ./hello_world` will not produce any errors. -- You are receiving this mail because: You are watching all bug changes.
