Result for 031D9AF851907C95EE09E9D0C9E1887FCB79A3B2

Query result

Key Value
FileName./usr/bin/valgrind-di-server
FileSize31056
MD54CFD5ECE909231568850496C9D333DD3
SHA-1031D9AF851907C95EE09E9D0C9E1887FCB79A3B2
SHA-25637D6B555EE09B8899028808317CD44AF737A648884221F4C936A955EAAEFE97D
SSDEEP768:7SOcCgfCNXUs0PoAXMHcpkn6/DJvdGZP:7S9CgfCNrn6/6
TLSHT1B4D22BDAFA5286ABCDF97F36429FD3B0A33B605273C9060AB79CC72D15563404B14B92
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