Result for 0A1D3E9F664F7A656A1BA0988663E2D62302D461

Query result

Key Value
FileName./usr/lib/valgrind/memcheck-s390x-linux
FileSize2636824
MD55B81D0B83AB1E5F7F2375E801427AFB4
SHA-10A1D3E9F664F7A656A1BA0988663E2D62302D461
SHA-2560EF7E393FD951254EDE9D3A2EC739A2C6F4F6018331E68E577A3D6FCC9DAD50E
SSDEEP24576:zFYMukZvgiduIu7RWPe14wOuVxRlyBo8WiDg6Y8Sl1h/LmeUigKevCk4:CLygid8g84UWCaDal1h/mnBvy
TLSHT144C53CA6A975CA95E4616D33E21179F1826F7E391BC4620CAEACF3C508F3343C215DE9
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
MD55E6099F355A7D2DB30F812D8BC3D0804
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.
PackageNamevalgrind
PackageRelease293.d_t.2
PackageVersion3.18.1
SHA-13F855EDD6B151667AA9F215C41AFB25CA3379FD9
SHA-256EDD27D865D4FFFE891A6A0A0C0B560CB6BC7A28261967D91DA8F337426D58F9F