Result for 01CC503B1554B2F4D0A534404C8DD0791F8B1F9F

Query result

Key Value
FileName./usr/lib/valgrind/drd-s390x-linux
FileSize3664880
MD50FFBD0DCFD6C58B9099DB762EB6A3CD4
SHA-101CC503B1554B2F4D0A534404C8DD0791F8B1F9F
SHA-2566AFD349C69CC9E451E61B6314555F26FD16876C5817D1CE78F63A33045049CEC
SSDEEP49152:XUg8vQLQzwlbj8MszGXqrBzo/JeZPEoXF:OEX3gPEGF
TLSHT192065CA7D8B1D291D0612E73F1665AF1937778340BD4771DBEB9E79208F32898308AB1
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
MD5C0E3E7A1C1A2CDD27D14335C303AB296
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
PackageRelease150600.1.3
PackageVersion3.22.0
SHA-19A9530E099B653E7508D87E00C9076FCE4C1F654
SHA-256C70789BCD2EBA039CC464F9FE0E7C1C750B456A446D659AA5785877CF71832A5