Result for 0377903F023A5733727D1B674E97D14C16D1D376

Query result

Key Value
FileName./usr/bin/cg_merge
FileSize39128
MD5584857B12C87F7232CC0FC6A6DC3B3B4
SHA-10377903F023A5733727D1B674E97D14C16D1D376
SHA-25672BC695714684EFF3899D6D418987C7F0C67BC31795B7E7F6B71B986C7037229
SSDEEP768:TXq6JvEoRIpqy1us4jB8PQuEOf/EKInEUkk:T6tqMb498PQuEyCx
TLSHT11403A6CAE110D296D0743933B2274BB2AA2774766BC9F3289B8DDF2B5CD1345491873A
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
MD55E6099F355A7D2DB30F812D8BC3D0804
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.2
PackageVersion3.18.1
SHA-13F855EDD6B151667AA9F215C41AFB25CA3379FD9
SHA-256EDD27D865D4FFFE891A6A0A0C0B560CB6BC7A28261967D91DA8F337426D58F9F