Result for 01693E3BEE9B1B5A6DA6676BBDE5BE0F05F21696

Query result

Key Value
FileName./usr/libexec/valgrind/getoff-amd64-linux
FileSize14448
MD5C743E092976FF625F30A3E0460B9FD58
SHA-101693E3BEE9B1B5A6DA6676BBDE5BE0F05F21696
SHA-256DD98669B1A0AEEC786009C293EEF98802A69B475B04E88A83FD95114AD4044D1
SSDEEP96:GlA1T/ERKj8DqApycwk3oDLLNS6qMU/YHHRk4sLlLuHi1liXKY0:GOgRKj8DqApycwk3kgNwHRFsZAi1lU
TLSHT150529643D3568A7FC26C53748883073575B3A4B097A24B3B596C62391E827818E7BDAE
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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
MD5A2D5D610AE6B33E2CCB52E58667A831A
PackageArchx86_64
PackageDescriptionWhen 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 []
PackageMaintainertv <tv>
PackageNamevalgrind
PackageRelease1.mga7
PackageVersion3.15.0
SHA-196270112958A06F762C2484EE310AE743A952E40
SHA-25691D7100A3C81053AA38CDCADF7E02E11FAFA5F7EA92A525AF6EC9D2B86813029