Result for 04BA637D3EE5F623EC9850AA70F6ADAD316095FB

Query result

Key Value
FileName./usr/share/doc/packages/valgrind/html/dh-manual.html
FileSize19513
MD5987E330B99FF60F3AEAF29983D0E5829
SHA-104BA637D3EE5F623EC9850AA70F6ADAD316095FB
SHA-2562047A3CCC645A0D9B919E67CAF4A6FF8FFC02817F0D2A9666CFF9A6A1AD7F2B0
SSDEEP384:t2JLMaqt2MxU2rN87ck9tlQrAItq3+5asSsR1b+OW:iw2RaNwrQro3+Q
TLSHT1AF92C632D36417A607C303E1FFA81B99A3A2812DE7725654B0FDC2385B45EED4B3625E
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