When I run valgrind, I get a reported error: ==734== 3,600 bytes in 90 blocks are definitely lost in loss record 8 of 10 ==734== at 0x4A05809: malloc (vg_replace_malloc.c:149) ==734== by 0x547BDFD: ??? ==734== by 0x547C4C9: ??? ==734== by 0x547CC16: ??? ==734== by 0x5473078: ??? ==734== by 0x547511F: ??? ==734== by 0x5475D0A: ??? ==734== by 0x54796C5: ??? ==734== by 0x32640E546B: getservbyport_r@@GLIBC_2.2.5 (in /lib64/libc-2.5.so) ==734== by 0x32640EAE9E: getnameinfo (in /lib64/libc-2.5.so) ==734== by 0x4EABF07: mt_cside_nio::InetAddress::getHostName(char*, int) (InetAddress.cpp:92) ==734== by 0x4D3056: mt_cside_nio::InetAddressTest::testGetHostName() (InetAddressTest.cpp:55) So I run with --gen-suppressions=yes and I get: { <insert a suppression name here> Memcheck:Leak fun:_vgrZU_libcZdsoZa_malloc obj:* obj:* obj:* obj:* obj:* obj:* obj:* fun:getservbyport_r@@GLIBC_2.2.5 fun:getnameinfo fun:_ZN12mt_cside_nio11InetAddress11getHostNameEPci fun:_ZN12mt_cside_nio15InetAddressTest15testGetHostNameEv } Which I add to a local file with <insert ... nane here> replaced. When I rerun valgrind with --suppressions=local.filename, valgrind apparently ignores the file. What am I doing wrong? Daniel
This hasn't changed in a long time. If you add '-v' do you see a line like --31835-- Reading suppressions file: local.filename?
Can you provide the info previously requested?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!