Date: Thu, 9 Dec 2004 23:08:41 +0000 (UTC) From: Pav Lucistnik <pav@FreeBSD.org> To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: ports/devel/valgrind Makefileports/devel/valgrind/files Makefile ports/devel/valgrind-snapshot/files patch-coregrind-vg_proxylwp.c Message-ID: <200412092308.iB9N8fkt095393@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
pav 2004-12-09 23:08:41 UTC
FreeBSD ports repository
Modified files:
devel/valgrind Makefile
devel/valgrind-snapshot Makefile
Added files:
devel/valgrind/files patch-coregrind-vg_proxylwp.c
devel/valgrind-snapshot/files patch-coregrind-vg_proxylwp.c
Log:
- 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)
Revision Changes Path
1.9 +1 -1 ports/devel/valgrind-snapshot/Makefile
1.1 +10 -0 ports/devel/valgrind-snapshot/files/patch-coregrind-vg_proxylwp.c (new)
1.11 +1 -1 ports/devel/valgrind/Makefile
1.1 +10 -0 ports/devel/valgrind/files/patch-coregrind-vg_proxylwp.c (new)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412092308.iB9N8fkt095393>