Result for 08DC8440755D6C4B612C2BE884A983F8EB7681B9

Query result

Key Value
FileName./usr/lib64/valgrind/vgpreload_drd-amd64-linux.so
FileSize149552
MD5D361EEE28E5F59D5A1C3144F5D0F96E6
SHA-108DC8440755D6C4B612C2BE884A983F8EB7681B9
SHA-256F24157BD27C839002676AD6342066245BBC95DC02D75805FC65EE6B29586786B
SSDEEP1536:lR9b50jGZ0XANQ6Fl1D+neeV99RRRETTmiQEYY:lRt0XANQ6Flk8Y
TLSHT11AE309193635C1ACD0DBC6F1F9DBD9F025E8B47013291A26AF81A76E39B8586112CF73
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