Result for 0C44135B7083E27E115E17B28512B0838CCD5384

Query result

Key Value
FileName./usr/share/doc/packages/valgrind/html/manual-core.html
FileSize161559
MD56F5EB2CA37D4F8C1AC11013FC3565B4F
SHA-10C44135B7083E27E115E17B28512B0838CCD5384
SHA-2560AF9F5F2D3172214C0FE0B63CA3331A79550187DCFECEED48529566300A9971B
SSDEEP3072:I+padwJM+0g1Laqa/dZ/javFwN2iHlxIYj7m4o8hihh:IaJX1Laqa/dZ/javFwN2iHjhiTL
TLSHT16FF3E823EA801373059382D9699923B9B7AFD13ED37119943DFDC32C1B06DA1827F59A
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
MD57F5E6FA00C350A9BB1497C9331FDF11F
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
PackageReleaselp150.3.3
PackageVersion3.13.0
SHA-1B5FC50E8C5F9FFC5CCA2840B0C41934F87813B28
SHA-2562A7719795B864DAC00EB5C21DCFD458C841633B1E12096A0372946C3A72CC6BA