Result for 0AC0383FA3B92DA5E30C93737EAC0D0B69C8DC29

Query result

Key Value
FileName./usr/lib64/valgrind/memcheck-amd64-linux
FileSize2545432
MD59BBB39683CD0DE121D2D5C40C5948317
SHA-10AC0383FA3B92DA5E30C93737EAC0D0B69C8DC29
SHA-256AD4750D2FA39861DF8E3F86DE4D2863A5CBB38D439F7C1779595B6567E73B7B8
SSDEEP49152:QRSTeM3ru/ODfdumi36lqZLC+8BWrzAz1tHPsOP:u+UcYhCZSAz1tHPJP
TLSHT115C55B56B1A324FCC617D53086B79232F834B89C43357EBB76D49F702E65D241B2AE22
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
MD53C699137E6466408C378D6D4D1E7D279
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
PackageReleaselp151.3.1
PackageVersion3.14.0
SHA-1867D0D99AA73B87E16F4F81EC2160F3FEC42DC38
SHA-256D7B66FE19063C90E7E8F6F5449317EB159C34D8AE3FF060179BE8ABE20462EFF