Result for 0BDBF3D6119433EA6693428284D1FAC5A5A552E6

Query result

Key Value
FileName./usr/share/man/man1/valgrind-di-server.1.gz
FileSize1099
MD5749F8793FD284EFB2CFAFD4EA41AA8CC
SHA-10BDBF3D6119433EA6693428284D1FAC5A5A552E6
SHA-2560AAB3BB8911DDE8261A42C8F5A4C9A2E34EB1F82E246BCF29257068F9DC44A96
SSDEEP24:XGOmNyAklo7aK03ihyChzocjlCP002An1cORDSqTjWmfl7jT2N:X7mNyAbaK0eZU00JpDdjhjT2N
TLSHT1B511B9D8FB068C811B8647B498735281954EA9932B88D45E54D2BFCE71D5F059F97021
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD57F099E4A01DB20A61008E030A9CFBA8D
PackageArchs390x
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
PackageRelease150500.2.1
PackageVersion3.20.0
SHA-1E8DE8A1564ADC02DBB66DC438C6054ED64D00ED7
SHA-256AA75D88B58630D73CF9CD56B17670555D2B77BD3B03125C84EA2F6F63D1852CE
Key Value
MD54B878B8B2B26A3129F77C89F07BF31D8
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
PackageRelease150500.2.1
PackageVersion3.20.0
SHA-10F2655532BE9856A1E43959F360EB83D722B860F
SHA-256FB690DF331F4FC4892E9437C3405D047452C18ACCA48F708A6239C3E63C5E53C