Result for 03A5DCF1E77517B847BB2D8BDEE26676C80CDB6B

Query result

Key Value
FileName./usr/lib64/valgrind/cachegrind-amd64-linux
FileSize2288944
MD517CEF93B1FD0A4F011CEDC503F1216FA
SHA-103A5DCF1E77517B847BB2D8BDEE26676C80CDB6B
SHA-2566C160E48EE3F24948D1393F83555382A7DA1F050FCD873F1348393F508260C3F
SSDEEP24576:EsJVqbOO7+G2AxGB1ryGqNLb/COwUshaXApFr6Sk7caFn805:XVqbOOm12Gqhb/RJsh0ppr
TLSHT1FAB55C45B1A230FCC61BD47486B75632F870795C42357EBF66A48F722F65C202B2AE63
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
MD5B23A307ACBCA729DA38AC25CFD196540
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.
PackageNamevalgrind
PackageRelease286.d_t.1
PackageVersion3.16.1
SHA-1249B0110F9814DE1A6AE995304ABBEBF2E52BC0A
SHA-256800433CA1B25B563D28B20185C128E2B912D9D15FC7BDC303056A140A15EFA29