Result for 01DC3B6AD07E0D24ADA2BBD748DCDA78F6BFA05B

Query result

Key Value
FileName./usr/lib/valgrind/vgpreload_core-s390x-linux.so
FileSize5856
MD5ECC797043815F747C835F3946BD8EAEF
SHA-101DC3B6AD07E0D24ADA2BBD748DCDA78F6BFA05B
SHA-25676E10DD73B93C6A776EE811AAEF248B8D4EDDBBA58A4A4D903358729243D90C0
SSDEEP48:mMGSt+BWB9oMekjUe+AfRAfVGcsx6uCdbsyd0AbkSVX+P:mMGrBWBmMeYas0dbHrW
TLSHT135C14143E7628E6FC87C9738899F4770B33755A991554B0227A8D731ECA36440F629C1
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 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
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