Result for 0B0A6B1C23F2A55D96633D0E705454D4CCA89C51

Query result

Key Value
FileName./usr/libexec/valgrind/cachegrind-amd64-linux
FileSize2340552
MD594E9BB50BEA0A5C10B8C8B67E3A1B8CC
SHA-10B0A6B1C23F2A55D96633D0E705454D4CCA89C51
SHA-2569AF51829855BFF8FE541CADF47845CF42DDC304972924C3768CAA26D93696031
SSDEEP49152:/m1iPTgzjUUIavzl8Kn1Xzpcoxhy66O62666b6lH66h26666666Q66I66S966dPE:Q8gzjUUIavzvnlzpJhy66O62666b6lHI
TLSHT1B1B55B36A5B210F8C566C13046FB9276EC3438AD43317E7F79E4DB711E81D302B6A9A9
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