Result for 03F584428B33DB7E95D9424F23FC6CC34DD2290C

Query result

Key Value
FileName./usr/share/doc/packages/valgrind/html/dist.news.html
FileSize209677
MD5604ECC6CDD35504BAF6C0E87ACF75E78
SHA-103F584428B33DB7E95D9424F23FC6CC34DD2290C
SHA-25662EE6104788D88C28584EC17DD73C10AC2F111B636EE1DDE57375451DF6A75A5
SSDEEP1536:AnmgSuQ6+nXph/0/Rf+ter7RJw7Ln4XE1K8moNip//2N0jdindNw7hUiDu4Gzmi2:4SbBPkRJoLnf8daHw79Q+U94MUo7s
TLSHT1292407DDB47AF9F269E3221FB4AE7604D76946131324286B607633C0135B7892BD3B63
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