Result for 02F31AC0F17A16F0BC917E7D62466693793F59FE

Query result

Key Value
FileName./usr/libexec/valgrind/drd-x86-linux
FileSize2304588
MD5BFD2F48DDDD072E344B6A6644DFFE554
SHA-102F31AC0F17A16F0BC917E7D62466693793F59FE
SHA-2564704B4A2C752B13DAD099B4F64AF2DC3CD5962C51A6405A6196F070C5F5A8690
SSDEEP49152:dlo+Mi9OxP+2CtZnXDsI1eN5Gkm69fz/npFHBy:dlsR5+2qXDsI1k5GkJ9fzw
TLSHT1B9B56EE5D6C230F5F7A3E474610EE7625A712B2D9072AEF1FB8C0B8A35713512E29316
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
MD5BC248D5662D17E34938D4FDEFBDC0DD2
PackageArchi586
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
PackageRelease293.d_t.2
PackageVersion3.18.1
SHA-12460E52094D82E5E761A1F309E9EAE371836CA2B
SHA-256A95170F8CA743079007FF046EBD97AB6C6411798E4707ADF73C194AC37B277D8