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 10 tools:
- memcheck, the primary tool, a memory error detector
- helgrind and drd, thread error detectors
- callgrind and cachegrind, execution and cache profiling tools
- massif, a memory tracker
- dhat, a memory content profiler
- lackey, an example of using the framework
- none, does no instumentation and can check that Valgrind runs correctly
- exp-bbv, and experimental profiling tool using sampling
Valgrind was initially ported to FreeBSD by Doug Rabson.
===> The following configuration options are available for valgrind-3.28.0,1:
32BIT=off: Enable debugging of 32-bit programs (requires lib32)
DOCS=on: Build and/or install documentation
MANPAGES=on: Build and/or install manual pages
MPI=off: Enable build of MPI wrappers
===> Use 'make config' to modify these settings
*: Revise USES=python:... version range constraints
and strip all lower bounds of 3.9 or 3.10 because they are implied now.
python:3.9-X -> python:-X
python:3.9+ -> python
python:3.10-X -> python:-X
python:3.10+ -> python
(options such as ,build preserved)
devel/valgrind: patch for ifuncs
The work for simd support uses @gnu_indirect_function. When Valgrind sees
binaries using such function it expects to have its own ifunc_handler. Until now
there wasn't one for FreeBSD so Valgrind terminates with an abort.
This patch merges the fix maintainer and creator made upstream.
PR: 273955
Reported by: pjfloyd@wanadoo.fr (maintainer)
devel/valgrind: do not strip binaries
Valgrind binaries should not be stripped (at least, not the preload shared
libs).
PR: 273243
Reported by: pjfloyd@wanadoo.fr (maintainer)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
*/*: Remove redundant '-[0-9]*' from CONFLICTS
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".
Approved by: portmgr (blanket)
devel/valgrind: Update to 3.18.1 and switch to use sourceware
The FreeBSD port of Valgrind has now been merged upstream and a new
release of Valgrind is out, 3.18.1. This updates Makefile, distinfo and
pkg-descr to reflect that.
Also remove pkg-message which has been incorrect and obsolete for a fair time.
PR: 259224
Clean up all commented PORTREVISION and PORTEPOCH lines
No revision bump tool that we have cleans them up or deals with
them, so we end up with duplicated lines. Instead of implementing
that just clean up the 51 ports that do this.
PORTREVISION and PORTEPOCH can be set to 0 explicitly instead if
you need a reminder or placeholder.
devel/valgrind: Update to be based on release version of Valgrind 3.17
Also, re-assign the submitter as maintainer.
PR: 254506
Approved by: zeising (maintainer)
devel/valgrind(-devel): Fix compiler version detection hopefully forever
Every time a compiler major version is bumped, we run into this exact
same error:
===> Configuring for valgrind-3.10.1.20160113_7,1
...
checking for a supported version of gcc... no (10.0.0)
configure: error: please use gcc >= 3.0 or clang >= 2.9
Attempt to fix this for all versions in the future.
Other fix included: don't use undefined behavior to implement offsetof,
just use the official builtin function instead.
Approved by: zeising (maintainer)
MFH: 2020Q1
Grab valgrind ports
Grab valgrind ports, I know people outside the project who are interested in
this. Grab it in the interim.
If you are interested in helping out, please let me know!
Allow valgrind to build with Clang again.
This resolves runtime issues with deciphering clang-built binaries
using a newer dwarf format.
Reported by: adrian, dim
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
devel/valgrind{,-devel}: unbreak with gcc6 or later
checking for a supported version of gcc... no (6.3.0)
configure: error: please use gcc >= 3.0 or clang >= 2.9
===> Script "configure" failed unexpectedly.
Bump PORTREVISIONS for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
Use USES=pathfix where applicable.
PR: 213195
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D8093
Add a MANPAGES knob to devel/valgrind{-devel}
devel/valgrind/Makefile
devel/valgrind/pkg-plist
devel/valgrind-devel/Makefile
devel/valgrind-devel/pkg-plist
Add a MANPAGES option. valgrind's man pages are built with
docbook-xml, which has lots of dependencies. Disabling MANPAGES will
speed the build.
Reviewed by: bdrewery, brd
Approved by: bdrewery (ports, maintainer)
Sponsored by: Spectra Logic Corp
Differential Revision: https://reviews.freebsd.org/D6667
- Fix 32BIT build
- Fix plist under 32bit builds
- Fix build on 84amd64 by using GCC. Stass has suggested to me that
using clang may result in a broken runtime anyhow.
The error encountered was the one logged in r350881 about missing 'rdtscp'
instruction.
- Fix build occuring during 'make stage' phase.
This changes almost all the "gnomehack" only USE_GNOME cases to USES= pathfix.
If a port used other USE_GNOME items it was untouched.
The ports that used other USES were fixed by hand.
PR: ports/177081
Reviewed by: bapt
Approved by: portmgr (miwi)
- Fix build on amd64 with WITHOUT_LIB32 on 9+
- Use the same check for /usr/lib32/libc.so as the
virtualbox ports for consistency.
PR: ports/174563
Reported by: 4721@hushmail.com
new devel/pkgconf added to replace devel/pkg-config. new version of pkg-config
are no more self hosting so we are stuck with 0.25 version while pkgconf provide
the same set of features as 0.27 and a compatible frontend. A symlink to
pkg-config has been added for convenience and compatibility
This also introduces a new macro to use pkgconf in your ports:
USE_PKGCONFIG
it can take the following arguments:
- yes (meaning build only dep)
- build (meaning build only dep)
- run (meaning run only dep)
- both (meaning run and build dep)
From now USE_GNOME= pkgconfig is deprecated in favour of USE_PKGCONFIG
The old gnome macro has been modified to use pkgconf but still the sameway: run
and build dep to avoid large breakage.
While here fix some ports relying on pkg-config but not specifying it, fix some
ports broken because testing wrong .pc files, and fix ports using pkg-config
--version to determine pkg-config version instead of
pkg-config --modversion pkg-config like recommanded by pkg-config
With Hat: portmgr
Exp-runs by: bapt (pointhat-west), beat (pointyhat)
For ports maintained by ports@ where pkgconfig is one of the USE_GNOME deps
convert it to BUILD_DEPENDS. This avoids the problem of the bogus run dep
added by bsd.gnome.mk.
Backport two revisions from Valgrind svn to fix crash when debugging
binaries built with GCC 4.6+:
r11856 | tom | 2011-07-05 02:22:32 -0700 (Tue, 05 Jul 2011) | 2 lines
Implement some extra DWARF ops that gcc 4.6.1 seems to use. Fixes #275284.
r11904 | tom | 2011-07-21 08:07:26 -0700 (Thu, 21 Jul 2011) | 2 lines
DWARF comparisons should be signed. Patch from Jakub Jelinek.
Submitted by: Tom Russo <tvrusso sandia.gov>
PR: ports/166341
- Return my ports back to the pool. I was unable to make any fixes to
my ports in the past 3 weeks while ports were broken on any 10.x
machines, which means I'm unable to maintain them. So let people know
that there's no available support for them until things are back to
normal (which also means that anyone with spare time will be able
to fix them without getting approval).
- Udpdate to a new 3.6.1 snapshot.
Changes:
- Implement shm_unlink wrapper.
- Add support for SHM_ANON shm_open(2) path.
- Fix sycalls 0 and 198 (__syscall) handling.