Key | Value |
---|---|
FileName | ./usr/libexec/valgrind/exp-bbv-amd64-linux |
FileSize | 2334056 |
MD5 | 275C3ED4BCBFD7A0698F2ACE7DC3735A |
SHA-1 | 04BED8AEB566CFAE5C61D616E9642C4EA0FF2BE1 |
SHA-256 | 4B8AA32874B412D3BA1F429654428D3C5B29D54B779FB7375C50A6EB3C91CECC |
SSDEEP | 24576:9gRjGjuqwWYO5r1LfqlMwUSMnu8uJ7r8xyEFRMMeuA/ID:9gRjeuqwWf5dfqlMDnu8uJcXMIA |
TLSH | T1D2B55A7578B620F8C5A2C57046B79272D835389E83327F6F29F4CA702E91D303B5EA65 |
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 | 2B4B141EEF94C31CE95E306FD94800F6 |
PackageArch | x86_64 |
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 unaddressible memory to system calls * Mismatched use of malloc/new/new [] vs free/delete/delete [] |
PackageMaintainer | tv <tv> |
PackageName | valgrind |
PackageRelease | 10.mga8 |
PackageVersion | 3.16.1 |
SHA-1 | 29AFDF3A701B4077B42A8578962BD193D4AE7C9E |
SHA-256 | F6A9B0CE1DDD72025264AB5624CCA3BA90CC605F50B209322196C358F0683472 |