Result for 064C85E8E2A67947AA13B0EAAD9311D1EAF929A0

Query result

Key Value
FileName./usr/libexec/valgrind/none-s390x-linux
FileSize2386840
MD5B9AF9344EED737CE104E60020A316366
SHA-1064C85E8E2A67947AA13B0EAAD9311D1EAF929A0
SHA-25643164EF4385A27D1CC87CC159F21EA942AEF18F4851E03A67023C15A8CDE1736
SSDEEP24576:AiK4Gtgu00haF7IO8bKZZpiiEcKYO3+YLwbI5pgrBMUDzNXvGA6YKIIUIIIIIIaY:hZZFcNZCpYLwbI4qiNd6Fb9q
TLSHT14DB54C869534CA62E0B22933B25679F1D77ABD395AC0470DADECF38648F7346C2254F2
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