Result for 05FCD53E57DE6189E330D6D9F1CB288099663492

Query result

Key Value
FileName./usr/lib/valgrind/memcheck-s390x-linux
FileSize2636824
MD57F02EFD51CF09A7AD7CF3798867B0EB5
SHA-105FCD53E57DE6189E330D6D9F1CB288099663492
SHA-256EA616C1768A902E9134EBA18644635540227E74A72FFE421B7E7C9F2EBC36A2C
SSDEEP24576:VFYMukZvgiduIu7RWPe14wOuVxRlyBo8WiDg6Y8Sl1h/LmeUigKevCk4:oLygid8g84UWCaDal1h/mnBvy
TLSHT194C53CA6A975CA95E4616D33E21179F1826F7E391BC4620CAEACF3C508F3343C215DE9
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
MD53DBED4B2C5F379EBE00878ABA1112724
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.1
PackageVersion3.18.1
SHA-1449F8FCCEE5DFF0F7F7D3CD85D5DE5D6F2FE8064
SHA-2560DE1FBF348CD0C5F0856FD403D08F19169EFED62A647BE061FB809F552FC0D88