Table of Contents

Valgrind

The recommended installation method is FreeBSD Ports & Packages.

Installation

Note: There may be some differences or delays between binary package versions and port versions, depending on whether you use Quarterly or Latest package branch.

Stable Version

The devel/valgrind port follows the official Valgrind release cycle, which is roughly aligned with the RedHat Fedora release cycle, with bi-annual releases targeted for April and October.

Install using either:

Development Version

The devel/valgrind-devel port will install a version of Valgrind that is tracking the upstream git repository, and is updated if/when there are sufficient fixes between official Valgrind releases.

Install using either:

Building from Source

Pre-Requisites

Building valgrind requires the following ports to be installed:

Obtaining the Valgrind Source

Starting with Valgrind 3.18.1 FreeBSD support has been integrated into the main Valgrind codebase. Prior to 3.18.1 (though still maintained) the source was hosted on on GitHub

To check out pre-3.18.1 versions of the source: 

git clone https://github.com/paulfloyd/freebsd_valgrind.git

The mercurial bitbucket repo that was the basis of the FreeBSD Valgrind port up to 3.17 is no longer accessible.

Building

sh autogen.sh
./configure
gmake
gmake install

TODO

  1. Implement a FreeBSD fair scheduler. Linux has a futex based scheduler. It uses come GCC __sync builtins (also available with clang). And a couple of syscalls for futex. Shouldn't be too hard to port to use _umtx_op.
  2. Implement rfork.
  3. Improve vgdb-invoker.
  4. Implement some form of lldb-server.
  5. Improve core dumps. Currently they are just Linux style core dumps with a FreeBSD tag.
  6. Add freeres support to libc FreeBSD Bugzilla Issue #259294
  7. Much needs to be done for Clang OMP.
  8. Fix handling of thread TLS allocation for Helgrind.