Result for 08523DA7F8FF75BEE6EDED00A88FD10FFF001539

Query result

Key Value
FileName./usr/bin/cg_merge
FileSize22808
MD59836468401613B8C74ECF7941F297C3D
SHA-108523DA7F8FF75BEE6EDED00A88FD10FFF001539
SHA-2566E4D03943B5FBE7FBB376D0B05B5ADD44190C676EEB8149F235A5CA1962CCED5
SSDEEP384:dXI96IFEEAioaNfpdh1xfMT6dwpq+Qytv3:d4Y+Ex9qxdh1xf+q+Ptv3
TLSHT189A21A56B25384BEC4A18334CBE3D566B670B410233663777644BA782E13F381E6FB96
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
MD57F5E6FA00C350A9BB1497C9331FDF11F
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://bugs.opensuse.org
PackageNamevalgrind
PackageReleaselp150.3.3
PackageVersion3.13.0
SHA-1B5FC50E8C5F9FFC5CCA2840B0C41934F87813B28
SHA-2562A7719795B864DAC00EB5C21DCFD458C841633B1E12096A0372946C3A72CC6BA