Result for 0ACCA7E80544EA5FC6219CDBA18427A061071AB9

Query result

Key Value
FileName./usr/share/doc/packages/valgrind/html/cl-manual.html
FileSize64786
MD54CA22F33B69DE33488EDEC728309CC15
SHA-10ACCA7E80544EA5FC6219CDBA18427A061071AB9
SHA-256106B5B6545F62E28B6AA9B37AE4F511DB076E1393F84E8A2251D8BA5010288BE
SSDEEP768:y3eb74Pe4JRzu7H48TbdfZDjs5c+mNowC4FSX:WebsPQXTbdp8D4oCSX
TLSHT1D453C816E2501377159752E962AA23BC73BAE13FE370128079FD83AC0F46DE0917B59B
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