Result for 00D9BA11DFE54BC43EE972A8C75C0BBBC0DD08BB

Query result

Key Value
FileName./usr/lib/valgrind/vgpreload_dhat-amd64-linux.so
FileSize87952
MD50CDA8F2221842D6D5E92936435CAF1CC
SHA-100D9BA11DFE54BC43EE972A8C75C0BBBC0DD08BB
SHA-256287F933A1D46644BD2846E9BFA30BF050C0C055EBDD2D75DAB29FA21041741EE
SSDEEP768:D+5eh2u6uJE2qnQXWBsmANQ6FlXr747A1Pqu+I5Ub4xOxcoDBGcUmp6IKcd4tgg0:DCs2u64Eb0MANQ6FlrMH1ZhQwmgDYo
TLSHT19883742D7532D0BDD4DDC2F0D83F95F468E9B46423261A237F82F33A39A48155A6CA39
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
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