Result for 05E6F1B56065E01DF8B0478DA59861E188A89F58

Query result

Key Value
FileName./usr/lib64/valgrind/vgpreload_massif-amd64-linux.so
FileSize30616
MD5DCECECC9EAD50F5BC3A34ADCD1CF743B
SHA-105E6F1B56065E01DF8B0478DA59861E188A89F58
SHA-2565011FBD66D7D4FB95FC4485CECA8C0B82DCAAD89ABD5A9C5D588D9032040D789
SSDEEP384:5b5drtRkZRniR1GAatVxJUotovk8MDmcwNsQzT6ylFg3:V5/fR1Gn4SocjycrQim
TLSHT1BBD2F03E7A36D4BDD4EED3B1E82FD1F478E87464632506167B82A37A24A4454092CF3E
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
MD53C699137E6466408C378D6D4D1E7D279
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://bugs.opensuse.org
PackageNamevalgrind
PackageReleaselp151.3.1
PackageVersion3.14.0
SHA-1867D0D99AA73B87E16F4F81EC2160F3FEC42DC38
SHA-256D7B66FE19063C90E7E8F6F5449317EB159C34D8AE3FF060179BE8ABE20462EFF