Date: Wed, 24 Apr 2024 20:13:07 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 278566] devel/valgrind: __sysctlbyname looks like false positive detect Message-ID: <bug-278566-7788-bndFCawUa8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-278566-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-278566-7788@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=3D278566 --- Comment #8 from Paul Floyd <pjfloyd@wanadoo.fr> --- (In reply to Ivan Rozhuk from comment #7) It would make the code too complex. Using the version macros as it is, I th= ink, is of dubious value. It's the way it's been done since the beginning for Da= rwin and FreeBSD so I'll stick with that for now. In general having a syscall wrapper on a system that doesn't have that sysc= all isn't a problem - normally the syscall will never get called (or at least v= ery rarely, I have seen cases where developers probe for syscalls by making inv= alid calls and then checking for ENOSYS or EINVAL). --=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-278566-7788-bndFCawUa8>