| Key | Value |
|---|---|
| FileName | ./usr/libexec/valgrind/dhat-arm64-linux |
| FileSize | 1994584 |
| MD5 | 2A42F2E94DF67BCD2748629D8A2FBA08 |
| SHA-1 | 0769381658B95F3C91D725E3F7555F3BBFE40D36 |
| SHA-256 | 7064FC58D1738A071ADB42EE55D66A5A68D3CEFC727EC1020A416070DEC3CB8C |
| SSDEEP | 24576:1G2NphjU9PXEJVEW++G3W/ceKeMyeTU+Bl2DP0lUj//7cKgJw+EAppjaCpkCJOEP:cWhjYjo58vNR/ |
| TLSH | T170958DED754F3D72EA8BE174A91DCB21F2133DACC26F60433812728467B2655C6F6826 |
| 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 | 0B949E1A9C88CEB2EDFF3555A12C075E |
| 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 unaddressible memory to system calls * Mismatched use of malloc/new/new [] vs free/delete/delete [] |
| PackageMaintainer | tv <tv> |
| PackageName | valgrind |
| PackageRelease | 1.mga7 |
| PackageVersion | 3.15.0 |
| SHA-1 | 56C6A589EC20EEA0DBB5E097473E4F429AD57662 |
| SHA-256 | 33F43932787D07AE0EDEF9E0E9A42F0A41001F3C9899FA75C0B7B79C98A0F3DF |