diff options
| author | V3n3RiX <venerix@redcorelinux.org> | 2018-07-14 20:57:42 +0100 |
|---|---|---|
| committer | V3n3RiX <venerix@redcorelinux.org> | 2018-07-14 20:57:42 +0100 |
| commit | 1798c4aeca70ac8d0a243684d6a798fbc65735f8 (patch) | |
| tree | e48e19cb6fa03de18e1c63e1a93371b7ebc4eb56 /dev-util/valgrind/metadata.xml | |
| parent | d87262dd706fec50cd150aab3e93883b6337466d (diff) | |
gentoo resync : 14.07.2018
Diffstat (limited to 'dev-util/valgrind/metadata.xml')
| -rw-r--r-- | dev-util/valgrind/metadata.xml | 28 |
1 files changed, 0 insertions, 28 deletions
diff --git a/dev-util/valgrind/metadata.xml b/dev-util/valgrind/metadata.xml deleted file mode 100644 index 31d1b4f644dd..000000000000 --- a/dev-util/valgrind/metadata.xml +++ /dev/null @@ -1,28 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> -<pkgmetadata> - <maintainer type="person"> - <email>blueness@gentoo.org</email> - <name>Anthony G. Basile</name> - </maintainer> - <maintainer type="person"> - <email>wizardedit@gentoo.org</email> - <name>Austin English</name> - </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 - - - 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> |