summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaurice van der Pot <griffon26@gentoo.org>2004-10-28 19:33:05 +0000
committerMaurice van der Pot <griffon26@gentoo.org>2004-10-28 19:33:05 +0000
commitbfa49a0678ad49cebf42b46f741ca860b6676c4f (patch)
tree5b33373aa394a02ec93e2ee9b35f7cfe26e36a01 /dev-util/valgrind/metadata.xml
parentForgot to remove digest files. (Manifest recommit) (diff)
downloadgentoo-2-bfa49a0678ad49cebf42b46f741ca860b6676c4f.tar.gz
gentoo-2-bfa49a0678ad49cebf42b46f741ca860b6676c4f.tar.bz2
gentoo-2-bfa49a0678ad49cebf42b46f741ca860b6676c4f.zip
Picked up maintenance of valgrind
Diffstat (limited to 'dev-util/valgrind/metadata.xml')
-rw-r--r--dev-util/valgrind/metadata.xml34
1 files changed, 16 insertions, 18 deletions
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>