Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Feb 2025 21:01:23 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 282576] Memory leak in sysctlbyname FreeBSD 14.1-RELEASE-p5 GENERIC x64
Message-ID:  <bug-282576-227-wCnYWnol4X@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-282576-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-282576-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282576

Mark Johnston <markj@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|secteam@FreeBSD.org         |bugs@FreeBSD.org
         Resolution|---                         |Not A Bug
                 CC|                            |markj@FreeBSD.org
             Status|New                         |Closed

--- Comment #2 from Mark Johnston <markj@FreeBSD.org> ---
markj@xinde> valgrind -s ./a.out=20
=3D=3D21570=3D=3D Memcheck, a memory error detector
=3D=3D21570=3D=3D Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward =
et al.
=3D=3D21570=3D=3D Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyr=
ight info
=3D=3D21570=3D=3D Command: ./a.out
=3D=3D21570=3D=3D=20
FreeBSD Kernel Version: FreeBSD 15.0-CURRENT #322 main-n275473-5778cbdae761:
Sun Feb 16 05:03:29 UTC 2025
    root@pkg-main:/usr/obj/root/freebsd/amd64.amd64/sys/GENERIC-NODEBUG

=3D=3D21570=3D=3D=20
=3D=3D21570=3D=3D HEAP SUMMARY:
=3D=3D21570=3D=3D     in use at exit: 4,096 bytes in 1 blocks
=3D=3D21570=3D=3D   total heap usage: 2 allocs, 1 frees, 4,251 bytes alloca=
ted
=3D=3D21570=3D=3D=20
=3D=3D21570=3D=3D LEAK SUMMARY:
=3D=3D21570=3D=3D    definitely lost: 0 bytes in 0 blocks
=3D=3D21570=3D=3D    indirectly lost: 0 bytes in 0 blocks
=3D=3D21570=3D=3D      possibly lost: 0 bytes in 0 blocks
=3D=3D21570=3D=3D    still reachable: 0 bytes in 0 blocks
=3D=3D21570=3D=3D         suppressed: 4,096 bytes in 1 blocks
=3D=3D21570=3D=3D=20
=3D=3D21570=3D=3D ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 fr=
om 0)
--21570--=20
--21570-- used_suppression:      1 MEMCHECK-LIBC-REACHABLE-1
/usr/local/libexec/valgrind/default.supp:595 suppressed: 4,096 bytes in 1
blocks
=3D=3D21570=3D=3D=20
=3D=3D21570=3D=3D ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 fr=
om 0)

The suppression in question is used for an allocation that happens in libc:

{
   MEMCHECK-LIBC-REACHABLE-1
   Memcheck:Leak
   match-leak-kinds: reachable
   fun:malloc
   obj:*/lib*/libc.so.7
   obj:*/lib*/libc.so.7
   obj:*/lib*/libc.so.7
   fun:vfprintf_l
}

Other than that, valgrind doesn't report any leaks.  Although you tested on
14.1, I strongly suspect that it's the same false positive there.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282576-227-wCnYWnol4X>