dev-util/valgrind/metadata.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
        <herd>no-herd</herd>
        <maintainer>
                <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

                - 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>
1	solar	1.1	<?xml version="1.0" encoding="UTF-8"?>
2			<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
3			<pkgmetadata>
4			<herd>no-herd</herd>
5			<maintainer>
6	chriswhite	1.1.1.1	<email>griffon26@gentoo.org</email>
7	solar	1.1	</maintainer>
8	chriswhite	1.1.1.1	<longdescription>
9			Valgrind is a GPL'd tool to help you find memory-management problems
10			in your programs. When a program is run under Valgrind's supervision,
11			all reads and writes of memory are checked, and calls to
12			malloc/new/free/delete are intercepted. As a result, Valgrind can
13			detect problems such as
14	solar	1.1
15	chriswhite	1.1.1.1	- Use of uninitialised memory
16			- Reading/writing memory after it has been free'd
17			- Reading/writing off the end of malloc'd blocks
18			- Reading/writing inappropriate areas on the stack
19			- Memory leaks -- where pointers to malloc'd blocks are lost forever
20			- Passing of uninitialised and/or unaddressible memory to system calls
21			- Mismatched use of malloc/new/new [] vs free/delete/delete []
22			- Some abuses of the POSIX Pthreads API
23			</longdescription>
24	solar	1.1	</pkgmetadata>