Key | Value |
---|---|
FileName | ./usr/libexec/valgrind/callgrind-x86-linux |
FileSize | 2267748 |
MD5 | 41558D2AA3D65ACA9D393601C6F7CE2E |
SHA-1 | 045A889F92137D6A1AE753F3BC60ABAD7EE7F453 |
SHA-256 | AA04C78DB759C6743B49B858125D14405837D827A921130FE3FD91BFD0EBB37C |
SSDEEP | 49152:Vp2QudyTE/EEi5wUt3tgT+ObbOskwHhhX8R88H0/cuAm8RYiN8Rw7sAJj:HXudqEcEi5wUtdgCObisphh+ |
TLSH | T107A58D6DF15209F2F653D8F4745ADBA66671220E8136FDF2AF8B1B8532713223F26112 |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
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 |
---|---|
MD5 | C79F14CA151FB043000E4120E0032A91 |
PackageArch | i586 |
PackageDescription | When a program is run under Valgrind's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted. As a result, Valgrind can detect problems such as: * Use of uninitialised memory * Reading/writing memory after it has been free'd * Reading/writing off the end of malloc'd blocks * Reading/writing inappropriate areas on the stack * Memory leaks -- where pointers to malloc'd blocks are lost forever * Passing of uninitialised and/or unaddressable memory to system calls * Mismatched use of malloc/new/new [] vs free/delete/delete [] |
PackageMaintainer | tv <tv> |
PackageName | valgrind |
PackageRelease | 2.mga9 |
PackageVersion | 3.19.0 |
SHA-1 | AF6EB5608C71D330480103E018F4E6CEF4DE46F5 |
SHA-256 | 70DD830A6D030AB7D542CADA63AF0A05F66FA25E2BB7B0DA0CD4481CC5CC1D74 |