Valgrind did not handle the following sysarch calls, and thus crashed
immediately
o get_fsbase
o set_fsbase
o get_gsbase
o set_fsbase
- Valgrind no longer dumps core when its client application does. [2]
Valgrind-snapshot does contain for safing the client's core dump,
but it does not work (it resulted in a crash) and has therefore been
disabled.
- Fix crash with valgrind-snapshot when the application to debug
does not exists or cannot be accessed.
- Fix symlink farms for threading libraries. FreeBSD 4-7 are
handled. [2]
- Bump PORTREVISION
Reported by: Ulrich Spoerlein <q@galgenberg.net> [1],
Chris Gilbert <Chris@lainos.org> [2]
PR: ports/86007 [1]
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)
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>
