Result for 0A8AE141ED60046FEBAE7E275A4188C74878868E

Query result

Key Value
FileName./usr/lib64/valgrind/vgpreload_core-x86-linux.so
FileSize5336
MD5C139461A7CF857EBB9761840FEA5729F
SHA-10A8AE141ED60046FEBAE7E275A4188C74878868E
SHA-2565468E299F24DA3DA9A9091DB2BC1EB597389E095EA66D7A6FEF6D2BB26C4BA2B
SSDEEP96:uvd4stPMBWBjLBeLuLbGZxu+vZq5ZvK33yl:k08pLBQo3y
TLSHT1C7B1A40DFFF4EE62C8B57B38D0AB82746375CC480756EF2B368529153E576981602683
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
MD549B29F04FE04F4657E66BBCC19D3D5A7
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://bugs.opensuse.org
PackageNamevalgrind
PackageReleaselp152.3.3
PackageVersion3.15.0
SHA-17AEF454B23F9CD6B4889190062FD7BD2BB2AB5B9
SHA-256ED3019545C7F8DAA7AFEFFD4CE6C091325C532752D0901B28E4D1DBC2D88FB92