[Bug 278566] devel/valgrind: __sysctlbyname looks like false positive detect

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

            Bug ID: 278566
           Summary: devel/valgrind: __sysctlbyname looks like false
                    positive detect
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: rozhuk.im@gmail.com
                CC: pjfloyd@wanadoo.fr
                CC: pjfloyd@wanadoo.fr
             Flags: maintainer-feedback?(pjfloyd@wanadoo.fr)
 Attachment #250205 text/plain
         mime type:

Created attachment 250205
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=250205&action=edit
example code

--90284-- Set osrel for current process with value 1400511
==90284== Syscall param __sysctlbyname(name) points to uninitialised byte(s)
==90284==    at 0x4992CDA: __sysctlbyname (in /lib/libc.so.7)
==90284==    by 0x20185F: main (in
/home/rim/docs/Progs/FreeBSD/sysctlbyname_broken)
==90284==  Address 0x1ffc000466 is on thread 1's stack
==90284==  in frame #1, created by main (???:)
==90284==  Uninitialised value was created by a stack allocation
==90284==    at 0x2017F0: main (in
/home/rim/docs/Progs/FreeBSD/sysctlbyname_broken)
==90284== 

But in way that it used some args OUT only (kernel only write result), and all
100% bytes are initialized.

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