Result for 044649921AF1AF51128DEDD05B7EED028BB39C63

Query result

Key Value
FileName./usr/lib64/valgrind/exp-sgcheck-amd64-linux
FileSize2266816
MD565F7D0311597983068B5F2E1EB1CBF86
SHA-1044649921AF1AF51128DEDD05B7EED028BB39C63
SHA-256B9F29C79F3B1EB0EFE6B397E69C44E27EF69B9C4126D15F5CCBCBBC2344C6FC8
SSDEEP24576:WYb462V4KDu0TBYPmi8f4LvMsh0qn4U+/qJr5BfpdAHWKlYOum1yxxu5sxi7:WY52V/RBYOinDMseG4U+c/fk2KlYOT7
TLSHT195A56C55B1A234FCC657C53086B75232F970789C82357EBF79A48F711E96C202B2AE63
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