Key | Value |
---|---|
FileName | ./usr/bin/vgdb |
FileSize | 54664 |
MD5 | BB42485E0C8ED1A640BF92CCEF0AC6A8 |
SHA-1 | 07635FAA856D8ECCABC726641D1B77BA292A07A6 |
SHA-256 | 65A10FE4151090E2AFB905CB2A5998863B463E6B0AA8550B3182C6B6B3B0076B |
SSDEEP | 768:VtO2YH8RFpl+TjEhmgZ3HrQNfzMDJowLH44NpcowyGXoV44mSY+R9ja7CRxVY12:ZFpEGrvDJrk4ioV4sY+y4 |
TLSH | T1F133D5DF51D2AD72CD563DB81A73F25048324C1126C2A9F2BB1F1BEE75A66AF3712201 |
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 | 34B014F9D42940A56F9B56DEC825BA60 |
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 | 1.mga9 |
PackageVersion | 3.20.0 |
SHA-1 | 21FE14D9524CCCE98AACDA9E490FD34E3A3BFCD9 |
SHA-256 | 3FCC218E53B32A523DF3B3E378AA4A1B8685129C9BD91A92AEDBFA681680CC89 |