Closed nbriggs closed 3 years ago
This will be an easy fix. The syscall is already implemented, I just need to get the right version macros.
Yeah, I thought so, looking at what is there. Judging by the man pages, sysctlbyname has been there since FreeBSD 2.2.5
It's an old interface, but only recently made into a syscall.
For 12.2 syscalls go up to 575 https://github.com/freebsd/freebsd/blob/release/12.2.0/sys/kern/syscalls.master
I'll probably upgrade my main machine to 12.2 soonish. In the meantime I'll fix this and test on a VM.
Huh. Yeah, I just looked at the 12.1.0 to 12.2.0 changes in sys/kern/syscalls.master
Should be fixed with this:
To github.com:paulfloyd/freebsd_valgrind.git 854352d2e..b040f7bcc freebsd -> freebsd
I still get about 70 fails om amd64 (due to clang 10)
Yes, it's no longer reporting the unhandled syscall. Thanks.
valgrind version, from git:
ran into this report trying to memcheck an application on FreeBSD 12.2-RELEASE:
570 is sysctlbyname.
Looks as though you have that under an
#if (FREEBSD_VERS >= FREEBSD_13)
?