Installing Valgrind

Prerequisites

Building valgrind requires the following ports to be installed:

The current version of the Valgrind FreeBSD is maintained in a mercurial repository on bitbucket.org: https://bitbucket.org/stass/valgrind-freebsd

To check out the source:

hg clone https://bitbucket.org/stass/valgrind-freebsd

The old version is also available in the FreeBSD ports collection in devel/valgrind.

sh autogen.sh
./configure
gmake
gmake install

Exit with a suitable error message if the procfs sysctl aren't available. Valgrind currently exits with an obscure message.
Test more syscalls which are disabled and implement the missing ones (rfork mainly, others to come).
Push FreeBSD changes to upstream valgrind
- [PATCH]: FreeBSD support for valgrind in the Valgrind bug tracker
Fix exp-ptrcheck.
- Details?
Fix support for FreeBSD TLS
- http://people.freebsd.org/~marcel/tls.html FreeBSD TLS notes
- http://lwn.net/Articles/5851/ Linux TLS notes
- http://www.pastebin.ca/1798637 Test application [dead link]
Growable stack / SIGSEGV / kqueue signal delivery issue.
ptrace handlers

Tested by Sandvine Incorporated: SYS_sched_get_priority_max, SYS_sched_get_priority_min, SYS_sched_rr_get_interval
libVex doesn't know about atomic instructions, which are used heavilly in userland by threading primitives (libthr in primis) in order to implement locking mechanism. While a direct fix to libVex seems pretty much difficult, a short-circuit of atomic operations may be implemented and got in place for main libraries. Apparently 3.5.0 has atomic support