Result for 0A0BD40E9259275A67C7DCA21A67D2816A1BB5B2

Query result

Key Value
FileName./usr/lib/valgrind/vgpreload_dhat-x86-linux.so
FileSize95496
MD54B5CF451E1B0A85AC42A2654283F581B
SHA-10A0BD40E9259275A67C7DCA21A67D2816A1BB5B2
SHA-2565981A6F4DE5587AD3B54B8B2958891CEFBC36D23E4134E50DD2FCD07BF25ECE2
SSDEEP1536:hyYzEb0MANQ6FlK7UZPmjjjjjjjjjjje58:pEb0MANQ6FlK/jjjjjjjjjjjk
TLSHT19093B52D7C24C4B5C4B6F1F460DF87BA44295C29926B49A77AE73F1C3AF57132B08862
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
MD5504895B97518D6C5BEF5A1C2951B3C9E
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.
PackageMaintainerhttps://www.suse.com/
PackageNamevalgrind
PackageRelease150600.1.3
PackageVersion3.22.0
SHA-1FC0F7DEE97B90985493BB31B21A639E5D396A7E5
SHA-25611E5EC0EC88B3DA00620A508619C4ECB3AD635E928569F41DB8701789753C01C