Key | Value |
---|---|
FileName | ./usr/libexec/valgrind/vgpreload_core-amd64-linux.so |
FileSize | 18816 |
MD5 | BE3105525E75BB065F75C1F5F7BF6767 |
SHA-1 | 04F03BF61AC4E0EC3A1810D7DAD499E152D97ED0 |
SHA-256 | AD78E975C88CABA97AB048F93C66329C3F07A8CE9CA2652F16F0B5E968D93574 |
SSDEEP | 96:R9IbBWBTTUMdpZslW016/ofaue8Z8q0ajm8TGymNfRBXoXH6c/w7/fgBmBnbi+ER:RU8xTppSWJyngzN5VgW0MFi |
TLSH | T18782C656E3B1CD7BC678833898AB077833B5E86107A9D3231B2860781D53B986F1D9A1 |
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 |