Version information is as follows: ==9740== Memcheck, a memory error detector ==9740== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==9740== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==9740== Command: /usr/home/ben/projects/kanjivg/t/../www/memory.cgi -q c=6BC5 ==9740== Valgrind produced the following: --9740-- WARNING: unhandled syscall: 531 --9740-- You may be able to write your own handler. --9740-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --9740-- Nevertheless we consider this a bug. Please report --9740-- it at http://valgrind.org/support/bug_reports.html. My OS is like this: FreeBSD mikan 10.3-RELEASE-p11 FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:47:18 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 According to syscall.h, call 531 is #define SYS_posix_fadvise 531 My package for valgrind is up to date: # pkg upgrade valgrind Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking integrity... done (0 conflicting) Your packages are up to date.
The FreeBSD port of valgrind is a separate project that is not part of the upstream code base and is not maintained by us. You will need to report this to the people that maintain the FreeBSD port.
That said, if the FreeBSD port is mature enough, its maintainers should initiate talks about integrating it upstream.
Apparently this bug had already been reported: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212697