Key | Value |
---|---|
FileName | ./usr/libexec/valgrind/callgrind-arm-linux |
FileSize | 2083096 |
MD5 | 8BA1D1A0F2F25606BA8D327DD69EC85F |
SHA-1 | 001535C3A6132AAECB3C0DE682EA684DF4795C11 |
SHA-256 | 76A0E00C58AEE0D93693326D5573987049D74429D7A4DC6D05CABFFE9DA071A7 |
SSDEEP | 24576:SLHLkLxLyLBxC4J6y9Xd7nYIjf5YiQm3Ods6MT/rEOoHQM4dsPQx:siSFnnmbIOi66M4dsY |
TLSH | T124A55A0579104A2BD5E553BAFB0C920873136F36D3DA3106ED01EE7067EA92D163EAE7 |
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 | BD938A16A3F17852089DEDCAAD925311 |
PackageArch | armv7hl |
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 | 2B8EBD461ABC4817A0AB0885F56B71CBF649BF28 |
SHA-256 | 2BCFE735E9B09296331C0D6AE5DEE0ECC65F1A7DC33F05375024392E7A8C973D |