Result for 04F3707C09B115D8B83EFDE26CF5F69498D1322A

Query result

Key Value
FileName./usr/lib64/valgrind/vgpreload_core-x86-linux.so
FileSize5336
MD5914AA7CCC5AB5167AB86291E124B26C2
SHA-104F3707C09B115D8B83EFDE26CF5F69498D1322A
SHA-256E0446507CD142EC29B6342E9EA51F3FDA6FFF194D75D96FC29FC3FF4B0115311
SSDEEP96:uvdnstPMBWBjLBeLuLbGZzu+vZq5ZvK33yl:308pLBQS3y
TLSHT1FBB19309FFF4EE66C8F57738D0AF92745375DC4807569F2B36C129163E572984A02683
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