diff options
Diffstat (limited to 'dev-util/valgrind')
| -rw-r--r-- | dev-util/valgrind/ChangeLog | 5 | ||||
| -rw-r--r-- | dev-util/valgrind/metadata.xml | 34 |
2 files changed, 20 insertions, 19 deletions
diff --git a/dev-util/valgrind/ChangeLog b/dev-util/valgrind/ChangeLog index 7b149043616c..c428071518e1 100644 --- a/dev-util/valgrind/ChangeLog +++ b/dev-util/valgrind/ChangeLog @@ -1,6 +1,9 @@ # ChangeLog for dev-util/valgrind # Copyright 2000-2004 Gentoo Foundation; Distributed under the GPL v2 -# $Header: /var/cvsroot/gentoo-x86/dev-util/valgrind/ChangeLog,v 1.38 2004/09/24 01:44:17 caleb Exp $ +# $Header: /var/cvsroot/gentoo-x86/dev-util/valgrind/ChangeLog,v 1.39 2004/10/28 19:33:05 griffon26 Exp $ + + 28 Oct 2004; Maurice van der Pot <griffon26@gentoo.org> metadata.xml: + Taken up maintenance of valgrind. 23 Sep 2004; Caleb Tennis <caleb@gentoo.org> valgrind-2.2.0.ebuild: Marking x86 stable diff --git a/dev-util/valgrind/metadata.xml b/dev-util/valgrind/metadata.xml index 14b5556b418f..76ea83251e3c 100644 --- a/dev-util/valgrind/metadata.xml +++ b/dev-util/valgrind/metadata.xml @@ -2,25 +2,23 @@ <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata> <herd>no-herd</herd> -<!-- <maintainer> - <description>Package has no maintainer</description> + <email>griffon26@gentoo.org</email> </maintainer> ---> -<longdescription> -Valgrind is a GPL'd tool to help you find memory-management problems -in your programs. When a program is run under Valgrind's supervision, -all reads and writes of memory are checked, and calls to -malloc/new/free/delete are intercepted. As a result, Valgrind can -detect problems such as + <longdescription> + Valgrind is a GPL'd tool to help you find memory-management problems + in your programs. When a program is run under Valgrind's supervision, + all reads and writes of memory are checked, and calls to + malloc/new/free/delete are intercepted. As a result, Valgrind can + detect problems such as -- Use of uninitialised memory -- Reading/writing memory after it has been free'd -- Reading/writing off the end of malloc'd blocks -- Reading/writing inappropriate areas on the stack -- Memory leaks -- where pointers to malloc'd blocks are lost forever -- Passing of uninitialised and/or unaddressible memory to system calls -- Mismatched use of malloc/new/new [] vs free/delete/delete [] -- Some abuses of the POSIX Pthreads API -</longdescription> + - Use of uninitialised memory + - Reading/writing memory after it has been free'd + - Reading/writing off the end of malloc'd blocks + - Reading/writing inappropriate areas on the stack + - Memory leaks -- where pointers to malloc'd blocks are lost forever + - Passing of uninitialised and/or unaddressible memory to system calls + - Mismatched use of malloc/new/new [] vs free/delete/delete [] + - Some abuses of the POSIX Pthreads API + </longdescription> </pkgmetadata> |