Result for 08463BF46F6540C304E4456153DE8395350F99A2

Query result

Key Value
FileName./usr/bin/valgrind
FileSize22888
MD589EBF69F462B7786512007386267971F
SHA-108463BF46F6540C304E4456153DE8395350F99A2
SHA-2564C9A2546A4AB9BB7D16ACA87DE7DF52A15FAF5B02AE2EF4600CCBBA0B4EE716A
SSDEEP192:RweAw91unKFN3y/rsIDDrzHu90RZMqYKDpIPZltXPFhJbLAErUo85M+qp8tceeo9:TcDdDLHu90/xpCtzbsErjujDDL
TLSHT103A2E600F2D1527ED69FD738819359332671B89557262B3BB680AB703D13BB04B3ADA6
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