[Bug 232235] valgrind doesn't find trivial leak on head anymore, works on stable/11

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232235

            Bug ID: 232235
           Summary: valgrind doesn't find trivial leak on head anymore,
                    works on stable/11
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Keywords: regression
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: tuexen at freebsd.org
 Attachment #198117 text/plain
         mime type:

Created attachment 198117
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=198117&action=edit
Sample program leaking 1KB

When testing valgrind on a stable/11 amd64 system with the attached test
program leak.c results in what is expected:

tuexen at stable11:~ % cc -o leak leak.c
tuexen at stable11:~ % valgrind --leak-check=full ./leak
==56478== Memcheck, a memory error detector
==56478== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==56478== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==56478== Command: ./leak
==56478== 
==56478== 
==56478== HEAP SUMMARY:
==56478==     in use at exit: 1,024 bytes in 1 blocks
==56478==   total heap usage: 1 allocs, 0 frees, 1,024 bytes allocated
==56478== 
==56478== 1,024 bytes in 1 blocks are definitely lost in loss record 1 of 1
==56478==    at 0x4C255B5: malloc (in
/usr/local/lib/valgrind/vgpreload_memcheck-amd64-freebsd.so)
==56478==    by 0x4007BA: main (in /usr/home/tuexen/leak)
==56478== 
==56478== LEAK SUMMARY:
==56478==    definitely lost: 1,024 bytes in 1 blocks
==56478==    indirectly lost: 0 bytes in 0 blocks
==56478==      possibly lost: 0 bytes in 0 blocks
==56478==    still reachable: 0 bytes in 0 blocks
==56478==         suppressed: 0 bytes in 0 blocks
==56478== 
==56478== For counts of detected and suppressed errors, rerun with: -v
==56478== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

whereas on a head system (r339354) amd64 I get:

tuexen at epyc:~ % cc -o leak leak.c
tuexen at epyc:~ % valgrind ./leak
==1760== Memcheck, a memory error detector
==1760== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==1760== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==1760== Command: ./leak
==1760== 
==1760== 
==1760== HEAP SUMMARY:
==1760==     in use at exit: 0 bytes in 0 blocks
==1760==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1760== 
==1760== All heap blocks were freed -- no leaks are possible
==1760== 
==1760== For counts of detected and suppressed errors, rerun with: -v
==1760== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

-- 
You are receiving this mail because:
You are the assignee for the bug.