Commit graph

5 commits

Author SHA1 Message Date
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
Pav Lucistnik
f15f0ac4be - Teach configure script about FreeBSD 6
PR:		ports/70746
Submitted by:	Simon Barner <barner@in.tum.de> (maintainer)
2004-08-21 20:29:19 +00:00
Michael Nottebrock
f09f7467a3 GCC 3.4 fixes. 2004-08-01 17:18:21 +00:00
Pav Lucistnik
210c0b78e3 - Update to 352
PR:		ports/69553
Submitted by:	Simon Barner <barner@in.tum.de> (maintainer)
2004-07-25 17:02:00 +00:00
Kirill Ponomarev
f3b8752aaf Valgrind is a system for debugging and profiling un*x 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.

The Valgrind distribution includes five tools: two memory error
detectors, a thread error detector, a cache profiler and a heap
profiler.  Several other tools have been built with Valgrind.

Valgrind was ported to FreeBSD by Doug Rabson (http://www.rabson.org/).

Submitted by:	Doug Rabson <dfr@FreeBSD.org> and Simon Barner <barner@in.tum.de>
2004-05-23 17:00:03 +00:00