Key | Value |
---|---|
FileName | ./usr/libexec/valgrind/drd-x86-linux |
FileSize | 2267580 |
MD5 | 09E6194EBC42CCF35382DF2D441AC8E5 |
SHA-1 | 07E96A673CEBF4BF6E4485A31A1839439CE44716 |
SHA-256 | EA62667314676CE776521B22D941238F591218E69B1DDBF1A0AEB83C644BD861 |
SSDEEP | 49152:R+Pa/wErcAvenogv8JIwGLJXt+uDAMBM7Y+R8R88H0/cuAm8RYiN8Rw7sZ:R+Pwrr6oy8JIwGLJdVkMBMUq |
TLSH | T175A57B6CE51609F2F553E8F46656E7A646B1260E4137FEF1FF8B1B8435322223F29212 |
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 |