Bug 368873 - Please add FreeBSD to the supported OS list
Summary: Please add FreeBSD to the supported OS list
Status: RESOLVED DUPLICATE of bug 208531
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Other FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
Depends on:
Reported: 2016-09-15 23:31 UTC by Yuri
Modified: 2019-01-02 19:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Yuri 2016-09-15 23:31:21 UTC

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
Comment 1 Tom Hughes 2016-09-16 00:03:00 UTC
This isn't something we can just do - somebody will need to volunteer to bring the port to us and work with us to integrate it.

Supporting a new platform in valgrind is a significant amount of work and even though there is an existing port I'm sure it would need a fair amount of effort to bring it up to date and to respond to the inevitable review comments and requests for changes needed to merge it. We would really also want to have one or more people prepared to maintain it on an ongoing basis as none of the current developers will have any experience of FreeBSD or will be running any FreeBSD systems.
Comment 2 Ed Maste 2019-01-02 19:23:51 UTC

*** This bug has been marked as a duplicate of bug 208531 ***
Comment 3 Ed Maste 2019-01-02 19:24:19 UTC
Close as duplicate against existing FreeBSD support ticket