Result for 0456DF4F91B1947E3FD2E3193CC0E0027E32A0C3

Query result

Key Value
FileName./usr/bin/vgdb
FileSize64072
MD55EEA04E23C24154F1CBC47FCB1389CD3
SHA-10456DF4F91B1947E3FD2E3193CC0E0027E32A0C3
SHA-2561D91F12093510F780C7F8F5EE6C39F5A5001B2F4174460BD2F893388FA5D17C2
SSDEEP768:83F8GiB1A2Cewod/4TFYQqdq+gKk85s7XU1WIpsMqgs8Ij7tsBexAgz:8GVBrwod4Jqdq/Kkys7XU1nzDG/9
TLSHT1E653F5EBD336EBF9E8F53337822F95A22367243427476E196F5C970960F2B018624671
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
MD53DBED4B2C5F379EBE00878ABA1112724
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
PackageRelease293.d_t.1
PackageVersion3.18.1
SHA-1449F8FCCEE5DFF0F7F7D3CD85D5DE5D6F2FE8064
SHA-2560DE1FBF348CD0C5F0856FD403D08F19169EFED62A647BE061FB809F552FC0D88