Result for 04C6A1B47050EF5CDA63DCADD16FB0A4FB3A64AA

Query result

Key Value
FileName./usr/lib64/valgrind/dhat-amd64-linux
FileSize2276552
MD5DF23CD6DFF7F6D8799D424790C92CDE9
SHA-104C6A1B47050EF5CDA63DCADD16FB0A4FB3A64AA
SHA-2569ACBA41D8E2F7AACE7ADA02A87F19768DB949824633B2C09587407D4C9D0C292
SSDEEP24576:+76IbPJQtqi1C305signE6k4exh4vABB1tL5N/aokd37rTAVy:s6I1ti1C3ysdnNk4exhiA3DbUL4Vy
TLSHT1D6B56C55B16230FCC557D43086B76632F874785C42317EBF6AA88F722F66C602B2AD63
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
MD50ECDC0D6328DA878A4519927DC5AEF63
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-1EA2CBECCD25C0AAB0F1BE4FB11AE6DCD0169C837
SHA-25682622E4E6CED60F609DA879F4F0358EFA4387B926513C3912D0BA0AEFE820077