Result for 065996F585FEB7DF883C2F426092945C0F6A35E3

Query result

Key Value
FileName./usr/share/man/man1/cg_annotate.1.gz
FileSize1652
MD5FD0A6B2A93E233991AC27F3040DD0AE1
SHA-1065996F585FEB7DF883C2F426092945C0F6A35E3
SHA-2564D0FE5C5ED8095AA3FC07667932310C3CD920851A190423E87A41E34A6570B77
SSDEEP24:X1Vbhhst93LeAnHsEiltIPHAS8O49F1RLCzQB487aQLSLTHkpstvPfbI6ptWI:X1VthsD3iAnHpil9SS9FbP7MvnbptWI
TLSHT143313C415A920FC55B0FC54EB50BF977CB105DD3161406D200F26E4B0DE881AAB0E528
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