Result for 0D1E27620FC0EA7F2E4B47EDEDC81AC19C593BB8

Query result

Key Value
FileName./usr/lib/valgrind/vgpreload_massif-x86-linux.so
FileSize54532
MD5FF5F14DB2AEC7BBDDBB53AD54F89A251
SHA-10D1E27620FC0EA7F2E4B47EDEDC81AC19C593BB8
SHA-2563BA3F1B6C1BC157C564E208C7A40496270A2C2EB57E7FA38C0514942C1D625D1
SSDEEP768:wrHoTStEwXbtGB9MJvlMx3Kg6Y7BGQhyn00zy7VMb8CIR19vBdiN:L4ESxYaJdak
TLSHT1DA335F193C24C4A6C8B7F5F851DF837E552A5C65A22A81ABBBD73F0839F97431B08C52
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
MD5504895B97518D6C5BEF5A1C2951B3C9E
PackageArchx86_64
PackageDescriptionValgrind 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.
PackageMaintainerhttps://www.suse.com/
PackageNamevalgrind
PackageRelease150600.1.3
PackageVersion3.22.0
SHA-1FC0F7DEE97B90985493BB31B21A639E5D396A7E5
SHA-25611E5EC0EC88B3DA00620A508619C4ECB3AD635E928569F41DB8701789753C01C