Result for 062C10907FC1F8C172F2E3EBCBF3A0DF56C7E221

Query result

Key Value
FileName./usr/lib64/valgrind/callgrind-amd64-linux
FileSize2361400
MD5C7041589C49405247F246F0535F320A7
SHA-1062C10907FC1F8C172F2E3EBCBF3A0DF56C7E221
SHA-256DD43B793166CDF7DD9573FF345FDA4C075D86C5B50E61D49F3E3E064DAA8FFBB
SSDEEP49152:bIpXwh+xFlGvXbx1zKJE58ePN5IuxPeTH0cq:b4XIOy9r55l5PxPcHB
TLSHT146B56C15B1A230FCC657D13486B75232F974B89C82357EBF65A48F712E95C202B2EE63
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
MD549B29F04FE04F4657E66BBCC19D3D5A7
PackageArchx86_64
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://bugs.opensuse.org
PackageNamevalgrind
PackageReleaselp152.3.3
PackageVersion3.15.0
SHA-17AEF454B23F9CD6B4889190062FD7BD2BB2AB5B9
SHA-256ED3019545C7F8DAA7AFEFFD4CE6C091325C532752D0901B28E4D1DBC2D88FB92