Key | Value |
---|---|
FileName | ./usr/libexec/valgrind/lackey-arm64-linux |
FileSize | 1976896 |
MD5 | 4F3CF432ED6DBBC1997AC46ABD097006 |
SHA-1 | 0C6C3C1198C4D38C9C6EEC75489D739A645619A7 |
SHA-256 | CD9A8A3AE89C9862DF9F810F58C53173A28C2A3103E669E128BB8402564CDFA6 |
SSDEEP | 24576:gfv8UmQkl7KqMsnLCxr4u2R3tSILjJDsN+SwMTFVjb8YCEMP07v63CmzEB3KXHbA:9UPqMGBMDjX5tddc |
TLSH | T1E1957CED9A0E3CB1DF8AE1349D0D9952E2237DECC32E1057344221C46BF66E09BF9566 |
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 | CA243DC1241F7666EEE2DB4CD64BD537 |
PackageArch | aarch64 |
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 | C1E49225ED222747AF16F362180FE43CC1F3D45A |
SHA-256 | 9E406DAB1D4D5470B312A91E1E123FA14450F8E0DEE230E8A320E4EE3CFF31C1 |