Result for 0C57F8CE48B3A3E42791FDF7AC99B2755BB098B2

Query result

Key Value
FileName./usr/lib64/valgrind/lackey-amd64-linux
FileSize2078240
MD51A899E8FC9B246C6A6D41426E3B2D148
SHA-10C57F8CE48B3A3E42791FDF7AC99B2755BB098B2
SHA-25673CF28678EAABE39AE28867CD6473447C9DB807410B2A2ED219533649CF6FDE9
SSDEEP24576:NLlv7+/9cIlkazleJbmUO3SGXx7w8LB+STj0OeCmWz/6mBhBO2YAv9M:NJv5iUJExsg8STwCmWr6yOFYq
TLSHT176A57E11B1B210FCC567C57086B69522E874799C82367E7F3AE48E711E86D242F2FE63
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