Result for 01C5D987EE7C919C6239C32A846D6081167AAC4B

Query result

Key Value
FileName./usr/lib/valgrind/vgpreload_drd-x86-linux.so
FileSize202084
MD51706D4E5F72E43FE5B271EC8088BB899
SHA-101C5D987EE7C919C6239C32A846D6081167AAC4B
SHA-2562E90BA356C0CD6D956D6A64F1A923096E183301A6EE65A1B30877CCE11D9CF08
SSDEEP3072:BAUREq0MANQ6FlT9dmgggggBhhhhhPGGGGG6y:BAsEq0NzmgggggBhhhhhPGGGGG6
TLSHT11C14542E7C38C1D6C432B4F6949BAB2B411D9C65922A95AF7BC63F1C39FC1971708D82
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
MD5F8B82299EC0440781233A3080A974141
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
PackageRelease293.d_t.3
PackageVersion3.18.1
SHA-131DF6CE15AB19049FA6E664D12AA1698605F93ED
SHA-256F5281155E9AD3054B2377C834FA895DB77C02D68F478150782AFBFD04D546637