Result for 055E3B4170FF24C3C285C479F14084DE23D1612F

Query result

Key Value
FileName./usr/bin/valgrind
FileSize22816
MD513CEC5F7D4992D3147022F7D49CFE1AF
SHA-1055E3B4170FF24C3C285C479F14084DE23D1612F
SHA-2562290160D4AAFBBFF9EF83B7C046352FA0F68085FFBD6C1D327CDDF2F9862A7C9
SSDEEP384:9OD4DOimPZROP5PGPRPXIsmPePe6XWXlWvFPJPPJPHBLPDS+PrPr7GIF0z4PW5m:cuYhYx+5QsmmWVV+tx5L7S+Tj7GISZ5m
TLSHT1A5A2844E66B5C696C874AB3BC9CA5BF37B7B2D206795021CABEDE3550473B10C680F21
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
MD5B319EF7630457B3CB8FB79C4D9E3C7E6
PackageArchs390x
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-162373897F23DE8155DBAAF3B7FDCCE98C33750CF
SHA-256FD3395F858630753F5108628BA12B517011968452015CC491619EE03382521F3