The FreeBSD Ports Archive

FreeBSD devel : valgrind

A (memory) debugging and profiling tool

 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/). 

valgrind history

v. 1.25
date: 2007/10/04 23:08:39;  author: edwin;  state: Exp;  lines: +0 -10
Remove always true/always false OSVERSION conditions.

v. 1.24
date: 2007/10/04 00:41:10;  author: edwin;  state: Exp;  lines: +1 -13
Remove always-false/true conditions based on OSVERSION 500000

v. 1.23
date: 2007/09/30 04:46:47;  author: linimon;  state: Exp;  lines: +2 -2
Switch autoconf dependencies from 2.53 or 2.59 to 2.61.

PR:		ports/116639
Submitted by:	aDe

v. 1.22
date: 2007/09/08 00:59:20;  author: linimon;  state: Exp;  lines: +0 -4
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:		portmgr

v. 1.21
date: 2006/05/04 21:41:10;  author: edwin;  state: Exp;  lines: +0 -1
Remove USE_REINPLACE from all categories starting with D

v. 1.20
date: 2006/02/20 13:07:57;  author: barner;  state: Exp;  lines: +1 -1
- SHM fix: Silence erroneous warnings on X server initialization
- Bump PORTREVISION

Submitted by: anholt

v. 1.19
date: 2005/10/20 10:41:02;  author: barner;  state: Exp;  lines: +1 -1
- Add support for uuidgen(2) system call
- Bump PORTREVISION

Submitted by:	rodrigc
PR:		ports/87697

v. 1.18
date: 2005/09/20 00:40:08;  author: barner;  state: Exp;  lines: +23 -4
- 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  [1],
		Chris Gilbert  [2]
PR:		ports/86007 [1]

v. 1.17
date: 2005/08/11 13:26:19;  author: barner;  state: Exp;  lines: +16 -9
- 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 
Approved by:	portmgr (kris)

v. 1.16
date: 2005/05/19 16:56:20;  author: barner;  state: Exp;  lines: +1 -1
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 
PR:		ports/81249

v. 1.15
date: 2005/04/12 03:25:19;  author: obrien;  state: Exp;  lines: +1 -1
At Kris's request, back out the MACHINE_ARCH spelling correction until
after 5.4-RELEASE.

v. 1.14
date: 2005/04/11 08:02:01;  author: obrien;  state: Exp;  lines: +1 -1
Assist getting more ports working on AMD64 by obeying the
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.

v. 1.13
date: 2005/02/28 13:05:24;  author: barner;  state: Exp;  lines: +1 -1
Change email address in ports maintained by me to barner@FreeBSD.org

Approved by:	arved (mentor)

v. 1.12
date: 2004/12/27 11:41:40;  author: vs;  state: Exp;  lines: +27 -3
- 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;   maintainer

v. 1.11
date: 2004/12/09 23:08:41;  author: pav;  state: Exp;  lines: +1 -1
- 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  (maintainer)

v. 1.10
date: 2004/12/08 19:36:55;  author: pav;  state: Exp;  lines: +1 -0
- Take care of leftover pkgconfig directory

PR:		ports/74818
Submitted by:	Simon Barner  (maintainer)

v. 1.9
date: 2004/09/02 05:15:19;  author: sem;  state: Exp;  lines: +0 -1
Remove junk from Makefile.

Reported by: Amir Shalem 

v. 1.8
date: 2004/09/01 16:27:20;  author: sem;  state: Exp;  lines: +5 -1
Rename devel/calltree to callgrind.
Update it to 0.9.8.
Update related ports.

PR:		ports/70936
Submitted by:	maintainer

v. 1.7
date: 2004/08/06 12:36:34;  author: lofi;  state: Exp;  lines: +1 -1
Correct CONFLICTS. valgrind-snapshot conflicts with every version of
valgrind, not just 352.

v. 1.6
date: 2004/08/06 12:25:54;  author: lofi;  state: Exp;  lines: +0 -3
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.

v. 1.5
date: 2004/08/01 15:20:03;  author: lofi;  state: Exp;  lines: +8 -0
valgrind installs different files on RELENG_4 & RELENG_5, add some
PLIST_SUB to deal with that.

v. 1.4
date: 2004/08/01 00:45:56;  author: lofi;  state: Exp;  lines: +2 -0
Disable procfs check on package builders.

v. 1.3
date: 2004/07/25 17:28:13;  author: pav;  state: Exp;  lines: +4 -8
- Use canonical way to request new Perl

v. 1.2
date: 2004/07/25 17:01:59;  author: pav;  state: Exp;  lines: +1 -1
- Update to 352

PR:		ports/69553
Submitted by:	Simon Barner  (maintainer)

v. 1.1
date: 2004/05/23 17:00:03;  author: krion;  state: Exp;
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  and Simon Barner 
=============================================================================


v. 1.25
date: 2007/10/04 23:08:39;  author: edwin;  state: Exp;  lines: +0 -10
Remove always true/always false OSVERSION conditions.

v. 1.24
date: 2007/10/04 00:41:10;  author: edwin;  state: Exp;  lines: +1 -13
Remove always-false/true conditions based on OSVERSION 500000

v. 1.23
date: 2007/09/30 04:46:47;  author: linimon;  state: Exp;  lines: +2 -2
Switch autoconf dependencies from 2.53 or 2.59 to 2.61.

PR:		ports/116639
Submitted by:	aDe

v. 1.22
date: 2007/09/08 00:59:20;  author: linimon;  state: Exp;  lines: +0 -4
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:		portmgr

v. 1.21
date: 2006/05/04 21:41:10;  author: edwin;  state: Exp;  lines: +0 -1
Remove USE_REINPLACE from all categories starting with D

v. 1.20
date: 2006/02/20 13:07:57;  author: barner;  state: Exp;  lines: +1 -1
- SHM fix: Silence erroneous warnings on X server initialization
- Bump PORTREVISION

Submitted by: anholt

v. 1.19
date: 2005/10/20 10:41:02;  author: barner;  state: Exp;  lines: +1 -1
- Add support for uuidgen(2) system call
- Bump PORTREVISION

Submitted by:	rodrigc
PR:		ports/87697

v. 1.18
date: 2005/09/20 00:40:08;  author: barner;  state: Exp;  lines: +23 -4
- 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  [1],
		Chris Gilbert  [2]
PR:		ports/86007 [1]

v. 1.17
date: 2005/08/11 13:26:19;  author: barner;  state: Exp;  lines: +16 -9
- 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 
Approved by:	portmgr (kris)

v. 1.16
date: 2005/05/19 16:56:20;  author: barner;  state: Exp;  lines: +1 -1
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 
PR:		ports/81249

v. 1.15
date: 2005/04/12 03:25:19;  author: obrien;  state: Exp;  lines: +1 -1
At Kris's request, back out the MACHINE_ARCH spelling correction until
after 5.4-RELEASE.

v. 1.14
date: 2005/04/11 08:02:01;  author: obrien;  state: Exp;  lines: +1 -1
Assist getting more ports working on AMD64 by obeying the
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.

v. 1.13
date: 2005/02/28 13:05:24;  author: barner;  state: Exp;  lines: +1 -1
Change email address in ports maintained by me to barner@FreeBSD.org

Approved by:	arved (mentor)

v. 1.12
date: 2004/12/27 11:41:40;  author: vs;  state: Exp;  lines: +27 -3
- 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;   maintainer

v. 1.11
date: 2004/12/09 23:08:41;  author: pav;  state: Exp;  lines: +1 -1
- 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  (maintainer)

v. 1.10
date: 2004/12/08 19:36:55;  author: pav;  state: Exp;  lines: +1 -0
- Take care of leftover pkgconfig directory

PR:		ports/74818
Submitted by:	Simon Barner  (maintainer)

v. 1.9
date: 2004/09/02 05:15:19;  author: sem;  state: Exp;  lines: +0 -1
Remove junk from Makefile.

Reported by: Amir Shalem 

v. 1.8
date: 2004/09/01 16:27:20;  author: sem;  state: Exp;  lines: +5 -1
Rename devel/calltree to callgrind.
Update it to 0.9.8.
Update related ports.

PR:		ports/70936
Submitted by:	maintainer

v. 1.7
date: 2004/08/06 12:36:34;  author: lofi;  state: Exp;  lines: +1 -1
Correct CONFLICTS. valgrind-snapshot conflicts with every version of
valgrind, not just 352.

v. 1.6
date: 2004/08/06 12:25:54;  author: lofi;  state: Exp;  lines: +0 -3
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.

v. 1.5
date: 2004/08/01 15:20:03;  author: lofi;  state: Exp;  lines: +8 -0
valgrind installs different files on RELENG_4 & RELENG_5, add some
PLIST_SUB to deal with that.

v. 1.4
date: 2004/08/01 00:45:56;  author: lofi;  state: Exp;  lines: +2 -0
Disable procfs check on package builders.

v. 1.3
date: 2004/07/25 17:28:13;  author: pav;  state: Exp;  lines: +4 -8
- Use canonical way to request new Perl

v. 1.2
date: 2004/07/25 17:01:59;  author: pav;  state: Exp;  lines: +1 -1
- Update to 352

PR:		ports/69553
Submitted by:	Simon Barner  (maintainer)

v. 1.1
date: 2004/05/23 17:00:03;  author: krion;  state: Exp;
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  and Simon Barner 
=============================================================================