Key | Value |
---|---|
FileName | ./usr/bin/valgrind-di-server |
FileSize | 30076 |
MD5 | 7064F16B4AA9FF4353906B891E9B0C59 |
SHA-1 | 05A43ECB4935B76268F874C02E10F6DACF8F9EEC |
SHA-256 | 5B7CDC1C82C394827830B52373818C1CD544D8A47CAE94BB8E2ACF5468114407 |
SSDEEP | 384:fFBcq9N8KNq/ak4hPIP769SpBRfJd9XVyP1fvMVoIanCGDHNqxwHpDQsKyz:NWqcKhPIUSu13jIlGDtqdS |
TLSH | T1CBD26B91B992D472F0630E74954B86F7842058127FBEEEB2B70E835DB222BD46B13F45 |
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 |