From 8376ef56580626e9c0f796d5b85b53a0a1c7d5f5 Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Sat, 14 Jul 2018 21:03:06 +0100 Subject: gentoo resync : 14.07.2018 --- dev-util/valgrind/metadata.xml | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 dev-util/valgrind/metadata.xml (limited to 'dev-util/valgrind/metadata.xml') diff --git a/dev-util/valgrind/metadata.xml b/dev-util/valgrind/metadata.xml new file mode 100644 index 000000000000..31d1b4f644dd --- /dev/null +++ b/dev-util/valgrind/metadata.xml @@ -0,0 +1,28 @@ + + + + + blueness@gentoo.org + Anthony G. Basile + + + wizardedit@gentoo.org + Austin English + + + 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 + + -- cgit v1.2.3