| Key | Value | 
|---|---|
| FileName | ./usr/libexec/valgrind/helgrind-amd64-linux | 
| FileSize | 2469560 | 
| MD5 | 886F5E7EFB7127E237AC600449886F82 | 
| SHA-1 | 06CF2ED937F86ABA9E3271CDAFBF14069D0B6FD5 | 
| SHA-256 | 68238703D0277C5D58893597F7FA5EC5F71D2519E70B784FCF26B7F096E58514 | 
| SSDEEP | 24576:1u0C21VhP536tNxItQq3YHlu63SamNby0S7qfBNbNg6QRG5N:cXeVhRAIOo6iamNbDS7IFNg6v | 
| TLSH | T1ADB55B3575B210F8C5A6C8706AF76272EC34399D4331BF7B69B4C9B05F02D202BAE965 | 
| 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 | 49B03C279E46D9B69CD5559BD9B63971 | 
| PackageArch | x86_64 | 
| 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 | 1.mga9 | 
| PackageVersion | 3.20.0 | 
| SHA-1 | 9514B0C8FFEDEFFC445084A9A2B559CE74C514A4 | 
| SHA-256 | 5DF8930B386FCD301BC9216C062BB11802E7ECDBEBDE515C6AC6ED040D3BD0A6 |