Result for 04FE24693E9FDA9B8F194C4E6C4260AEAE55D0E3

Query result

Key Value
FileName./usr/lib64/valgrind/drd-amd64-linux
FileSize2968808
MD59935323614CD648EC36D9EEA45D077BA
SHA-104FE24693E9FDA9B8F194C4E6C4260AEAE55D0E3
SHA-2560C3DD71662C26B2C14F5FEDDD1F8BFD580ED7640D8CF09967CE2ED0E26CC6974
SSDEEP49152:hBJOJpc2v42TnfZdvXpQZ/XFO4LoQ3UYgUyJ2T0L6XFrr:hQS2QgR1xV27F
TLSHT12CD55B55B1A320FCC657D03086A75632F971B86D43313EBF69988B712F66C202B2ED67
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