Result for 07614F34C388422387DB680135A1F902B81CFCDD

Query result

Key Value
FileName./usr/lib64/valgrind/vgpreload_drd-amd64-linux.so
FileSize149552
MD573D377280B1BCB8B8E618BE25B6629AC
SHA-107614F34C388422387DB680135A1F902B81CFCDD
SHA-256913713DA5D5A3FC9174D5A33E98B4495D0C16064F800E6DAA824177A6639DDAD
SSDEEP1536:NR9b50jGZ0XANQ6Fl1D+neeVccRRRETTmiQEznna4E:NRt0XANQ6Flksza4E
TLSHT126E309193635C1ACD0DBC6F1F9DBD9F025E8B47023295A26AF81A76E39B4582112CF73
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
MD5B3146E24E5F900C4AC3E9A8A8426C570
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
PackageRelease288.d_t.1
PackageVersion3.16.1
SHA-1BAC988B9BD91AE58736B90C89541D2C283BF4B8F
SHA-2567B74FB067297AC2F6BC7DA1F98EC7C770F53E10A372BA0D268C95CA1104857D7