Pav Lucistnik 0b3795dfcf - Starting from some point after FreeBSD 5.2.1, valgrind did not terminate ...

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)

2004-12-09 23:08:41 +00:00

..

patch-configure

…

patch-coregrind-vg_proxylwp.c

- Starting from some point after FreeBSD 5.2.1, valgrind did not terminate

2004-12-09 23:08:41 +00:00

patch-helgrind_hg_main.c

…

patch-memcheck_mc_include.h

…