Parents (Total: 2)

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

Key	Value
MD5	504895B97518D6C5BEF5A1C2951B3C9E
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.
PackageMaintainer	https://www.suse.com/
PackageName	valgrind
PackageRelease	150600.1.3
PackageVersion	3.22.0
SHA-1	FC0F7DEE97B90985493BB31B21A639E5D396A7E5
SHA-256	11E5EC0EC88B3DA00620A508619C4ECB3AD635E928569F41DB8701789753C01C

Key	Value
MD5	C0E3E7A1C1A2CDD27D14335C303AB296
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.
PackageMaintainer	https://www.suse.com/
PackageName	valgrind
PackageRelease	150600.1.3
PackageVersion	3.22.0
SHA-1	9A9530E099B653E7508D87E00C9076FCE4C1F654
SHA-256	C70789BCD2EBA039CC464F9FE0E7C1C750B456A446D659AA5785877CF71832A5