Result for 0DA17EF6208EA3ED106365ED116F85CDBF75244D

Query result

Key Value
FileNameusr/share/doc/valgrind/html/dist.readme-solaris.html
FileSize13598
MD5E3121B57E62EEB0B15CDAFE0333F1028
SHA-10DA17EF6208EA3ED106365ED116F85CDBF75244D
SHA-2563DEC14CAECC5185AB1779ABB821D35F44317054CB3846D9AF3FCD1B016F72754
SHA-51236ADB7EF4B91DFC4A7D6CA09347F3A7285DB5590AA27371D482183CD4C3682973C9F0AF6F6FE494EBF243BFC2870AD4BD93A12ACB388D9EBA9D4226BEF4CD32B
SSDEEP192:oxa+BXmtyCSRKtJZUMfYl2d/16EDtLKItWP+0F2fnt/B8hp4V0:uGtekTZUMAl2xcOZKItWCnt/B84W
TLSHT1DA5262CA8CCDE4B51041E6BE75992D40F2E2B0DECADE341982B1DDB4671E58FF90E1A1
insert-timestamp1728223626.634724
mimetypetext/html
sourcesnap:YpugLgtZ7huGVdXgktDBXarl1BI0ylW9_24
tar:gnameroot
tar:unameroot
hashlookup:parent-total70
hashlookup:trust100

Network graph view

Parents (Total: 70)

The searched file hash is included in 70 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD568834E4B41E9D59A97EE12D439ECE66D
PackageArchs390x
PackageDescriptionValgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
PackageNamevalgrind
PackageRelease292.d_t.4
PackageVersion3.18.1
SHA-100D04B880C0130ADA8481375A044D94DC832F438
SHA-256DB02B5BEF4D6EF7ED05C0015AE2AE138819BFEC8EA81175C9934C7D81C3DF146
Key Value
FileNamehttp://dl-cdn.alpinelinux.org/alpine/latest-stable//main//s390x//valgrind-doc-3.19.0-r0.apk
MD57D266E96D333D1819B7B28626F545B4E
SHA-107BE6BA25C6A6D0477923D8D51568D052C62427E
SHA-256C3E352D0D561C4EEAFFA1214805AACBD475D653B3442FDEB4671FF16E149D203
SSDEEP98304:JbATGOurers9bGErJIm011xTzuvsK9VT0gT6hcAN9:iyOfa6SJJQxTzsSPh9
TLSHT191F533F4C221745F36BF8C2DF655A534120F0C26E29D8F6EAB2A4B28864DFB8E7D1544
Key Value
MD53F64B3A04210B0E62D730C0F32397B33
PackageArchx86_64
PackageDescriptionValgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
PackageNamevalgrind
PackageRelease293.d_t.2
PackageVersion3.18.1
SHA-10BE3E17E547AAE942B5ABE2F7E129CB40E59DE0E
SHA-25675E4A25173881C3A1EA2F0912C435D9953FF9072C59F3881702C0FE9B6A5BFDE
Key Value
FileNamehttp://dl-cdn.alpinelinux.org/alpine/latest-stable//main//x86//valgrind-doc-3.22.0-r0.apk
MD5A6EDE4A1EAF9FD24969128982E46325F
SHA-10EE1D60E18C813A9B72F8A8BE8214C88B5B7484C
SHA-256F2F6472F2517A0C32A2362A8F49CD8F3F21DF60A9FEDBD8A3CA1CD987DF8CF9E
SSDEEP98304:ARHI2vp6/g28yRSPOmbrzLqFaR1ZA6g+RPl9ZNp3ltKEMbMf5kWfJ8DyzNzPD:+HLsgNy6PbGofZA6g0d/Np1trfqUdzL
TLSHT1C53633398070FF04092F23CABE59B501552544AED6DD6C1EF0B72CA750E7AAC9F8A17B
Key Value
MD54B878B8B2B26A3129F77C89F07BF31D8
PackageArchx86_64
PackageDescriptionValgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
PackageMaintainerhttps://www.suse.com/
PackageNamevalgrind
PackageRelease150500.2.1
PackageVersion3.20.0
SHA-10F2655532BE9856A1E43959F360EB83D722B860F
SHA-256FB690DF331F4FC4892E9437C3405D047452C18ACCA48F708A6239C3E63C5E53C
Key Value
MD5AC6A9B26DD1AAFD296E2AD07DA98D62D
PackageArchppc64le
PackageDescriptionValgrind is an instrumentation framework for building dynamic analysis tools. There are Valgrind tools that can automatically detect many memory management and threading bugs, and profile your programs in detail. You can also use Valgrind to build new tools. The Valgrind distribution currently includes six production-quality tools: a memory error detector (memcheck, the default tool), two thread error detectors (helgrind and drd), a cache and branch-prediction profiler (cachegrind), a call-graph generating cache and branch-prediction profiler (callgrind), and a heap profiler (massif).
PackageMaintainerCentOS Buildsys <bugs@centos.org>
PackageNamevalgrind
PackageRelease7.el8
PackageVersion3.18.1
SHA-111662FECC81F0AE46936E1FD63FAFC728D79DA69
SHA-256B0DA57C67E677FA943D0CBDC479B148AFF2EFC6BFAAA8EB8AA5B3DD33C09475C
Key Value
MD5F914DF61780D6D5BA290643800D90135
PackageArcharmv7hl
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 unaddressable memory to system calls * Mismatched use of malloc/new/new [] vs free/delete/delete []
PackageMaintainertv <tv>
PackageNamevalgrind
PackageRelease2.mga9
PackageVersion3.19.0
SHA-117BF2F3F9D4B47FCB2926A231681311E1494000F
SHA-25664AE257D387A10936E1E3E13C797C2C1FF3102136118E8112F0114CCCEB97AC9
Key Value
FileNamehttp://dl-cdn.alpinelinux.org/alpine/latest-stable//main//armv7//valgrind-doc-3.21.0-r4.apk
MD550EB6326D000FFA38AF8597CBA056116
SHA-11A2E57E01DD2A627C82744549A4257FC8278660A
SHA-256237E1423E4005AEB7380DACF06C1D668811E5FA8FDE8708AE60A6B04037CFFA9
SSDEEP98304:c6aq2jumjFHkl7ZQF4WZSTPpEwOlJkSKzGKTJJcGV:cHj3oQF4WyPpE1ySKTff
TLSHT1933633E8A391B715308F775EA718EE2D86BF11FC8787682BCA2F1411570FD924E4A523
Key Value
FileNamehttp://dl-cdn.alpinelinux.org/alpine/latest-stable//main//s390x//valgrind-doc-3.23.0-r0.apk
MD59C6D61370E562459820451DFB06B70BA
SHA-11D4A65FE67DBB3BE4A5B9924994D93939E02BA0A
SHA-256605B481D49A5BF8FA1B2AE372F25244515958F275D80697AF0C7FDA83C5587C0
SSDEEP98304:IOuBOGOVyQDA2plnayrrd4OsTr6OxhjM00QHaXGFGVUYnJ7Gwk5:IbOGOlA2LaAJFsLnh0QGGs0
TLSHT1A52633FC1D66FF4032EF7D0ADADDEB140427121E864E1A3EF263052921BA569B748739
Key Value
MD55ED6038BDAF443F4D9A8FFA92242F5BB
PackageArchaarch64
PackageDescriptionValgrind is an instrumentation framework for building dynamic analysis tools. There are Valgrind tools that can automatically detect many memory management and threading bugs, and profile your programs in detail. You can also use Valgrind to build new tools. The Valgrind distribution currently includes six production-quality tools: a memory error detector (memcheck, the default tool), two thread error detectors (helgrind and drd), a cache and branch-prediction profiler (cachegrind), a call-graph generating cache and branch-prediction profiler (callgrind), and a heap profiler (massif).
PackageMaintainerCentOS Buildsys <bugs@centos.org>
PackageNamevalgrind
PackageRelease7.el8
PackageVersion3.18.1
SHA-11E1F61EB2443383060AD7EF3FBACC18205BAAAFE
SHA-25648BC1A007F32EC182E6B1B34FB052306EAFAFDA2B4526B49A44A1B1B6E3DD69E