Hi,

valgrind currently doesn't support FreeBSD OS. As a result, version on FreeBSD is delayed: FreeBSD still has  3.10.1 when 3.11.0 has been released almost a year ago.

De facto, valgrind works fine on FreeBSD. So it doesn't need to be brought up to speed, or anything like that. It just needs to be merged into and maintained as a part of the single upstream source tree.

The current problem is that the person maintaining valgrind's FreeBSD flavor doesn't manage to have time to sync with the upstream, so the version is lagging in BitBucket: https://bitbucket.org/stass/valgrind-freebsd

If you add another OS, you will find out that in the long run this is also beneficial for the project as a whole, because supporting more OSes will make valgrind itself cleaner and more generic. I myself created many FreeBSD ports, and I submitted hundreds of bug reports to various upstreams with bugs that were found because FreeBSD does things a bit differently than Linux. (For example, I found that the configure option in jq failed to turn the regex library off, or that tor fails to create the /var/run/tor/pid file when the enclosing directory doesn't exist. Nobody on linux ever tried these things.)

Please support FreeBSD! It is a very nice system, people who work with it never have anything bad to say about it.


Reproducible: Always