Result for 05F5554706F4E94A453B43DD408F3179EA2F6B06

Query result

Key Value
FileName./usr/bin/valgrind-di-server
FileSize31056
MD5604926A8832D5C710681D8ABE544870E
SHA-105F5554706F4E94A453B43DD408F3179EA2F6B06
SHA-2562ADEF6888889ED3E2E5CCD4FE586B7B11E2986A4E979AA5EFFF14A18757B4748
SSDEEP384:N7EFKCNfwiyEh1F+eULQBI0gTjn3/DlnaNv/nN11GrP4Dq/dVuqb06B:CFFf3jET/RaNv/N11GkDIdUuB
TLSHT19AD24CBB6932C295C5F47F3685DE92F06333653273CA071677DCC32A26A2310865AFA5
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
MD5B319EF7630457B3CB8FB79C4D9E3C7E6
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
PackageRelease286.d_t.1
PackageVersion3.16.1
SHA-162373897F23DE8155DBAAF3B7FDCCE98C33750CF
SHA-256FD3395F858630753F5108628BA12B517011968452015CC491619EE03382521F3