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	3F64B3A04210B0E62D730C0F32397B33
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	293.d_t.2
PackageVersion	3.18.1
SHA-1	0BE3E17E547AAE942B5ABE2F7E129CB40E59DE0E
SHA-256	75E4A25173881C3A1EA2F0912C435D9953FF9072C59F3881702C0FE9B6A5BFDE

Key	Value
MD5	C9CF7FAE2E3F3E4C1565DF54DC6BFF5D
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	293.d_t.2
PackageVersion	3.18.1
SHA-1	502A32353919F92FE61B5C9EA1F69F84ACFA8868
SHA-256	09B3D8DD98170218F8F15122A9649D34CE9637D58150183F606D2FB22FCE2F92