| Key | Value |
|---|---|
| FileName | ./usr/bin/vgdb |
| FileSize | 51224 |
| MD5 | B953169041267D9ED7CE1B4A802F12EB |
| SHA-1 | 09C1B72D093D6F92802680054C986FB355B64A81 |
| SHA-256 | E307FF2739714F8A2FEAA3F0EDD1BE54DE0D396C632B644D95D2F4A035947A23 |
| SSDEEP | 768:/7q1oM5aNTra67S2DFBKdD0Tng9z82mlw9hZeWCcv:/7q1o2ya67S2D+uTg9z8Jao |
| TLSH | T16633395FBA5E58E7E38B437ACB18E151B227B03C931281577B8533AD52CEB598FB0484 |
| 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 | 4287C11088AA824AD121D3C6AEEE940A |
| 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 | 2.mga9 |
| PackageVersion | 3.19.0 |
| SHA-1 | 2962AFCBC3589F072294F0307F9577AD86F33827 |
| SHA-256 | F9CE962CEFD8ECAD5AED9144FEFE83888C589FB518FE226D444A3D51328164DF |