- Update to 3.5.0-2: - Fix build of MPI wrappers [1] - Fix LDT handling in i386 case. - Fix socketpair(2) syscall wrapper. PR: ports/144067 [1] Reported by: "O. Hartmann" <ohartman@zedat.fu-berlin.de> [1]f086451dc7
Port details
devel/valgrind3.27.1,1
Memory debugging and profiling tool
- Maintainer
- pjfloyd@wanadoo.fr
- Packages
- valgrind 3.27.1,1
- Upstream
- Higher version available: 3.28.0
- CPE
valgrind:valgrindfrom the port- WWW
- https://www.valgrind.org/
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (150)
- Update project URL. PR: ports/146635 Submitted by: Edmondas Girkantas <eg@fbsd.lt>079ff5c053
- Update to newer snapshot fro P4.7e9d0708d1
- Bump PORTREVISION as the revision numbering scheme has changed. - Reformat pkg-descr for lines to not exceed 80 characters. Pointed out by: bsam Feature safe: yes32c704692e
- Remove the bogus PKGNAMESUFFIX that erroneously went in. Pointy hat to: me Feature safe: yes23db0e596a
- Do not try to build 32-bit support on amd64 if 32-bit libraries are not available. Suggested by: koitsu Feature safe: yes27408aa426
- Update to version 3.5.0. Feature safe: yes26ca396038
- Take maintainership.b17767c58b
- Fix build with NOPORTDOCS Approved by: miwi (mentor, implicit)2c1f0b8e5f
Reset barner@FreeBSD.org due to several months of inactivity. Hat: portmgra325795c3a
- Remove conditional checks for FreeBSD 5.x and olderd095d4a965
- Fix build from within jails PR: ports/127015 Submitted by: Alexander Churanov Approved by: portmgr (erwin)40b4b23017
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script. Specifically, newer autoconf (> 2.13) has different semantic of the configure target. In short, one should use --build=CONFIGURE_TARGET instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)741aa71483Conversion from (now defunct) autoconf-2.61 to autoconf-2.62 Tested by: exp build run (erwin)771ea13f41
Fix build on FreeBSD 7. Requested by: many PR: ports/116513 [1], ports/123711 [2] Submitted by: Bruce Cran <bruce@cran.org.uk> [1], delphij [2]7ce1a7216c
- Mark BROKEN on 7.x Reported by: pointyhat1c7683b04f
Mark IGNORE on 8.0: unsupported.c5c80f4df2
Remove always true/always false OSVERSION conditions.c947287940
Remove always-false/true conditions based on OSVERSION 500000ec7c5b0142
Switch autoconf dependencies from 2.53 or 2.59 to 2.61. PR: ports/116639 Submitted by: aDe48420a5ebd
Welcome bsd.perl.mk. Add support for constructs such as USE_PERL5=5.8.0+. Drop support for antique perl. Work done by: gabor Sponsored by: Google Summer of Code 2007 Hat: portmgr9839011ec3
- Fix build on -current. - Valgrind still dumps core (under investigation).c5fd6d2919
Remove USE_REINPLACE from all categories starting with D2406d49a61
- SHM fix: Silence erroneous warnings on X server initialization - Bump PORTREVISION Submitted by: anholt9effedd182
- Fix build on 7-current by avoiding conflict in si_band macro, that is already defined in the sys/signal.h header Submitted by: Niklas Sorensson <nik@cs.chalmers.se> Prodded by: kris via pointyhatff2d82068c
Add SHA256 for my ports (that don't already have it).f50a6c5196
Fix build on FreeBSD 6 and above. PR: ports/89056 Submitted by: "Andrei V. Shetuhin" <shetuhin@corp.mail.ru> Also reported by: kris via pointyhata168a326aa
- Add support for uuidgen(2) system call - Bump PORTREVISION Submitted by: rodrigc PR: ports/876973dc959b3ed
- fix build on 7-current [1] - Add forgotten internal dependency for FreeBSD 4. Reported by: mich [1]e8a2db3f9d
- Fix on FreeBSD 6 and above: [1] [2]
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]d711a485a0- Mark valgrind ports IGNORE when /proc is not mounted, previously, only 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)69f79551f5
- Fix detection of FreeBSD 7 Reported by: kris via pointyhat41a9ed248a
Fix generation of suppression files: Valgrind puts parts of its output on stderr, so the redirection into a file did not work. Submitted by: Eugene Kilachkoff <zeus@samaramail.ru> PR: ports/8124944ed78bd3a
At Kris's request, back out the MACHINE_ARCH spelling correction until after 5.4-RELEASE.c3d8037aeb
Assist getting more ports working on AMD64 by obeying the Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.f2fc2d60ae
Change email address in ports maintained by me to barner@FreeBSD.org Approved by: arved (mentor)b1ff38d266
- Add some suppression files & fix packaging[1] (bump PORTREV) - Warn if USER_LDT is not present in 4.x-kernel [2] PR: ports/71832 [1]; ports/75436 [2] Submitted by: Frerich Raabe; maintainer006ecc902e
- 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)0b3795dfcf
- Take care of leftover pkgconfig directory PR: ports/74818 Submitted by: Simon Barner <barner@gmx.de> (maintainer)5b4e49c639
Remove junk from Makefile. Reported by: Amir Shalem <amir(at)boom.org.il>d00fa4c616
Rename devel/calltree to callgrind. Update it to 0.9.8. Update related ports. PR: ports/70936 Submitted by: maintainer12ffbba738
- Teach configure script about FreeBSD 6 PR: ports/70746 Submitted by: Simon Barner <barner@in.tum.de> (maintainer)f15f0ac4be
Correct CONFLICTS. valgrind-snapshot conflicts with every version of valgrind, not just 352.2a2b628a45
Instead of just checking for PACKAGE_BUILDING, don't let the check for 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.21f68dd7f7
GCC 3.4 fixes.f09f7467a3
valgrind installs different files on RELENG_4 & RELENG_5, add some PLIST_SUB to deal with that.e90cae0339
Disable procfs check on package builders.9217f515c2
- Use canonical way to request new Perl3e25b2770e
- Update to 352 PR: ports/69553 Submitted by: Simon Barner <barner@in.tum.de> (maintainer)210c0b78e3
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>f3b8752aaf