Result for 0B75BEE43A1C787227DC0C30C33084E61799CC2A

Query result

Key Value
FileName./usr/lib64/valgrind/massif-amd64-linux
FileSize2293024
MD5FEC2E57DDB5CBE945D6FAB222EC69E7E
SHA-10B75BEE43A1C787227DC0C30C33084E61799CC2A
SHA-256272D94581CBE179CABD5D0E08485E95DEB050BFF23428D1C2FDBB3A9DCC7A95C
SSDEEP24576:zPfL3McDn7CQH/fKzRoHY1TpnOlDx6XdOTqRE5O+vdQ+hwpJ:z3LSwaz99n8d8dOTqRY1k
TLSHT100B55B55B1A230FCC617D43486B75632F970B95C42353EBF6AA48F712F65C202B2AE63
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
MD50ECDC0D6328DA878A4519927DC5AEF63
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.
PackageNamevalgrind
PackageRelease286.d_t.1
PackageVersion3.16.1
SHA-1EA2CBECCD25C0AAB0F1BE4FB11AE6DCD0169C837
SHA-25682622E4E6CED60F609DA879F4F0358EFA4387B926513C3912D0BA0AEFE820077