Result for 088BCBD128884DBF4D7D293CC4AE678923401235

Query result

Key Value
FileName./usr/lib/valgrind/massif-s390x-linux
FileSize2292704
MD529A1F29A416F169893E854E1E9A7EBF3
SHA-1088BCBD128884DBF4D7D293CC4AE678923401235
SHA-2561E453F255066210D4B27875B6DF2E378A264290EDDEDFB0B21195CCDF0F04774
SSDEEP24576:TtfFCpbpCtZ6KQOyA2NIV6PpcbvDb78MtylDQHGUZ9MXO:xfF+bpCtZtyA2OBD8MtycM
TLSHT17EB53B96A934CBA9E4B16933E11279F1D3AF7A390BC05A0C9EBCF35509F334182159F6
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