correctly, but got stuck in state ``umtx''. This was mentioned on the lists
and in kern/68992 [closed], but I was never able to fix the problem.
On FreeBSD >= 502120, the kernel's and valgrind's definition of
UMTX_CONTESTED flag were out of sync, which is why valgrind did not terminate
on these systems.
PR: ports/74903
Submitted by: Simon Barner <barner@gmx.de> (maintainer)
procfs stop the portbuild at all. Displaying a warning is fine, breaking
the build over a runtime requirement that does not break building the port
is not.
programs. With the tools that come with Valgrind, you can
automatically detect many memory management and threading bugs,
avoiding hours of frustrating bug-hunting, making your programs
more stable. You can also perform detailed profiling, to speed
up and reduce memory use of your programs.
This version is based on a more recent snapshot of
devel/valgrind and supports some older AMD processors.
Submitted by: Doug Rabson <dfr@FreeBSD.org> and Simon Barner <barner@in.tum.de>
