Result for 0CF9F66A3A5CB2CDDBE5550BD572276A7CFEECE1

Query result

Key Value
FileName./usr/lib/valgrind/exp-bbv-s390x-linux
FileSize2247608
MD55544BF78A3A4CB112A537546FBE3F844
SHA-10CF9F66A3A5CB2CDDBE5550BD572276A7CFEECE1
SHA-25634285D18A840E6FD290F9056E1483DBE3B5A127996E86DA4EB137E024C080B00
SSDEEP24576:aktXVEJiUI8OT1gUN9eCSckA9FvBgJcY5Zlxne8a+P5oa+g1h:akAW8OTeUmCStA9FEldabg1
TLSHT1EFA54C9AA534CB99D0726D33E21179F1C2AB7A391BD0664C6EACF38509F3343C215DE6
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
MD5F22DD25262B9301185E5EDA9F9A2DEAD
PackageArchs390x
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
PackageRelease293.d_t.1
PackageVersion3.18.1
SHA-1664D5777F53D2AF87CBE3C99644CA5E7C12BB0F3
SHA-256A547A30C71C3A31AAC4DDDCB61741B388F93EAD7E1D306BAC906C2FC7513DFD1