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]
a warning was printed.
A mounted procfs is a runtime dependency of valgrind, but since the
implementation of automatic suppression file generation the valgrind
binary is run in the post-install stage.
- An exception needs to be made for the ports cluster: The machine compiling
the list of IGNOREd ports does not have a mounted /proc, so the check (and
the generation of supression files is disabled there).
Users who want to suppress false positives in valgrinds output should build
the port instead of installing the package (so the rules can be customized to
their specific installation).
Reported by: Paul Ledbetter III <aeacides@gmail.com>
Approved by: portmgr (kris)
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)
procfs stop the portbuild at all. Displaying a warning is fine, breaking
the build over a runtime requirement that does not break building the port
is not.
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.
This version is based on a more recent snapshot of
devel/valgrind and supports some older AMD processors.
Submitted by: Doug Rabson <dfr@FreeBSD.org> and Simon Barner <barner@in.tum.de>
