Result for 0747036871EC7170F4CEDB0F153539027E2E2C81

Query result

Key Value
FileName./usr/lib/valgrind/vgpreload_helgrind-x86-linux.so
FileSize156956
MD5C583F7657FEF16E501910206F474777F
SHA-10747036871EC7170F4CEDB0F153539027E2E2C81
SHA-256B5C5D6C37030FA525D1B489104BA91D062184E20BBBB40217697E2D29C7F4189
SSDEEP1536:L9REfIQUbTrPH0MANQ6FlEyXaqPD3g/GGLsCqHi1Vd11dDgVC:LnE80MANQ6FlEy6LWagVC
TLSHT116E3A6AD3C28C491C472F4F5229ACF764518F92BB65A48B77E973F0936F83C11B0994A
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