Result for 0407FF2485A1B5275CB7F0979A034D0CCE1FC81C

Query result

Key Value
FileName./usr/libexec/valgrind/callgrind-s390x-linux
FileSize2567296
MD5B32DF21E458A7E5260CB2571D08F4723
SHA-10407FF2485A1B5275CB7F0979A034D0CCE1FC81C
SHA-256BF77F51AB035116C61EB27595CC0F7C0A28A05CBE5CE6DDD77DC95467CC0DE95
SSDEEP49152:dZoSaFJhnFn/Xi/ue+TNO7v+7Q4jhAgv:dZoZJRF6H+TNO7G7/j3v
TLSHT103C56C825934C962D0B12973B256B9F1DB6ABE395BC0470DADACF3C644F7385C2258F2
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
MD568834E4B41E9D59A97EE12D439ECE66D
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
PackageRelease292.d_t.4
PackageVersion3.18.1
SHA-100D04B880C0130ADA8481375A044D94DC832F438
SHA-256DB02B5BEF4D6EF7ED05C0015AE2AE138819BFEC8EA81175C9934C7D81C3DF146