Result for 07671DC673AB15543B190188482C35E5989E7905

Query result

Key Value
FileName./usr/lib64/valgrind/massif-amd64-linux
FileSize2107008
MD5D8CDD9CD1E6C826A0711644FF1184828
SHA-107671DC673AB15543B190188482C35E5989E7905
SHA-256132CC2CF89F20A7F113FF26666FFEE60BD6CE5E3EF20C0F8EEC4C8E4475F86CA
SSDEEP24576:71+7KfAgjlkqM8ZIIHM9YPRoYsZbY3QdH1Yz7ALFKEpe81Bnw1kLTEO2D:5jfAg9RoYKdmz7ArA81Nw8TEO
TLSHT1D7A56D15B1B210FCC567C57086B69532E874799C82327E7F39E48E721E86D242F2FE62
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
MD57F5E6FA00C350A9BB1497C9331FDF11F
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
PackageReleaselp150.3.3
PackageVersion3.13.0
SHA-1B5FC50E8C5F9FFC5CCA2840B0C41934F87813B28
SHA-2562A7719795B864DAC00EB5C21DCFD458C841633B1E12096A0372946C3A72CC6BA