Parents (Total: 5)

The searched file hash is included in 5 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	B23A307ACBCA729DA38AC25CFD196540
PackageArch	x86_64
PackageDescription	Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
PackageName	valgrind
PackageRelease	286.d_t.1
PackageVersion	3.16.1
SHA-1	249B0110F9814DE1A6AE995304ABBEBF2E52BC0A
SHA-256	800433CA1B25B563D28B20185C128E2B912D9D15FC7BDC303056A140A15EFA29

Key	Value
MD5	E58E87ED7C5D72D7FEE05AA071171997
PackageArch	s390x
PackageDescription	Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
PackageName	valgrind
PackageRelease	286.d_t.1
PackageVersion	3.16.1
SHA-1	5283BAB81461F9EB63621775FB8D03673181F8F8
SHA-256	A897DC0BB1763DD0C2303C6C363FE0B532F4DF8954619317367DBFE2A2AD7E73

Key	Value
MD5	0ECDC0D6328DA878A4519927DC5AEF63
PackageArch	x86_64
PackageDescription	Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
PackageName	valgrind
PackageRelease	286.d_t.1
PackageVersion	3.16.1
SHA-1	EA2CBECCD25C0AAB0F1BE4FB11AE6DCD0169C837
SHA-256	82622E4E6CED60F609DA879F4F0358EFA4387B926513C3912D0BA0AEFE820077

Key	Value
MD5	B3146E24E5F900C4AC3E9A8A8426C570
PackageArch	x86_64
PackageDescription	Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
PackageName	valgrind
PackageRelease	288.d_t.1
PackageVersion	3.16.1
SHA-1	BAC988B9BD91AE58736B90C89541D2C283BF4B8F
SHA-256	7B74FB067297AC2F6BC7DA1F98EC7C770F53E10A372BA0D268C95CA1104857D7

Key	Value
MD5	B319EF7630457B3CB8FB79C4D9E3C7E6
PackageArch	s390x
PackageDescription	Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
PackageName	valgrind
PackageRelease	286.d_t.1
PackageVersion	3.16.1
SHA-1	62373897F23DE8155DBAAF3B7FDCCE98C33750CF
SHA-256	FD3395F858630753F5108628BA12B517011968452015CC491619EE03382521F3