Result for 0BA962EA5931EBCD4A0B2A4003156CC60CBD8049

Query result

Key Value
FileName./usr/lib/valgrind/drd-s390x-linux
FileSize3607480
MD5F7A954A701E715F3453141806E834108
SHA-10BA962EA5931EBCD4A0B2A4003156CC60CBD8049
SHA-2565FDE3CB493024CF3AD7F61FCCADA9311D1F0A72C9CD6FE31DBFBA10E02E99C96
SSDEEP49152:QKEBhXeeZBhkpHHLtF++pzlGE3rAuahN9rrPPP0Apg:QRCDlDchN9rrPPP0R
TLSHT12AF55BA7D8B0D291D0A13E73F1565AB193777C340BD5771DBEA9E79208F32898308AB1
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
MD56D50CE5B06FADA66697D5254052DF6AD
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
PackageRelease150400.1.4
PackageVersion3.18.1
SHA-13E34F231C116F5C64B3FE48C9CC3F498711079FB
SHA-256FC394D9C32FD597BF065BB0FB967C65FA5CCBED610A346CAC93214660A09A2BB