freebsd-ports/devel/valgrind/files/patch-coregrind-vg_proxylwp.c

--- coregrind/vg_proxylwp.c.orig	Thu Dec  9 20:02:58 2004
+++ coregrind/vg_proxylwp.c	Thu Dec  9 20:03:16 2004
@@ -30,6 +30,7 @@
 
 
 #include "vg_include.h"
+#include "vg_unsafe.h"
 
 #ifndef UMTX_CONTESTED
 # if __FreeBSD_version < 502120
- 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-10 00:08:41 +01:00			`--- coregrind/vg_proxylwp.c.orig Thu Dec 9 20:02:58 2004`
			`+++ coregrind/vg_proxylwp.c Thu Dec 9 20:03:16 2004`
			`@@ -30,6 +30,7 @@`


			`#include "vg_include.h"`
			`+#include "vg_unsafe.h"`

			`#ifndef UMTX_CONTESTED`
			`# if __FreeBSD_version < 502120`