Parents (Total: 21)

The searched file hash is included in 21 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	68834E4B41E9D59A97EE12D439ECE66D
PackageArch	s390x
PackageDescription	Valgrind 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.
PackageName	valgrind
PackageRelease	292.d_t.4
PackageVersion	3.18.1
SHA-1	00D04B880C0130ADA8481375A044D94DC832F438
SHA-256	DB02B5BEF4D6EF7ED05C0015AE2AE138819BFEC8EA81175C9934C7D81C3DF146

Key	Value
MD5	3F64B3A04210B0E62D730C0F32397B33
PackageArch	x86_64
PackageDescription	Valgrind 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.
PackageName	valgrind
PackageRelease	293.d_t.2
PackageVersion	3.18.1
SHA-1	0BE3E17E547AAE942B5ABE2F7E129CB40E59DE0E
SHA-256	75E4A25173881C3A1EA2F0912C435D9953FF9072C59F3881702C0FE9B6A5BFDE

Key	Value
MD5	BC248D5662D17E34938D4FDEFBDC0DD2
PackageArch	i586
PackageDescription	Valgrind 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.
PackageName	valgrind
PackageRelease	293.d_t.2
PackageVersion	3.18.1
SHA-1	2460E52094D82E5E761A1F309E9EAE371836CA2B
SHA-256	A95170F8CA743079007FF046EBD97AB6C6411798E4707ADF73C194AC37B277D8

Key	Value
MD5	31780FA3B2A5564B9A1C0FF3056A7B9E
PackageArch	armv7hl
PackageDescription	Valgrind 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.
PackageName	valgrind
PackageRelease	294.d_t.1
PackageVersion	3.18.1
SHA-1	2A5D039A57CCEC026F048E04C38C25B7DEFA9C13
SHA-256	52CF37DA246648E0E073BB39EC997C484AD94F1FD5ACB885ABE5693630392770

Key	Value
MD5	F8B82299EC0440781233A3080A974141
PackageArch	x86_64
PackageDescription	Valgrind 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.
PackageName	valgrind
PackageRelease	293.d_t.3
PackageVersion	3.18.1
SHA-1	31DF6CE15AB19049FA6E664D12AA1698605F93ED
SHA-256	F5281155E9AD3054B2377C834FA895DB77C02D68F478150782AFBFD04D546637

Key	Value
MD5	6D50CE5B06FADA66697D5254052DF6AD
PackageArch	s390x
PackageDescription	Valgrind 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.
PackageMaintainer	https://www.suse.com/
PackageName	valgrind
PackageRelease	150400.1.4
PackageVersion	3.18.1
SHA-1	3E34F231C116F5C64B3FE48C9CC3F498711079FB
SHA-256	FC394D9C32FD597BF065BB0FB967C65FA5CCBED610A346CAC93214660A09A2BB

Key	Value
MD5	5E6099F355A7D2DB30F812D8BC3D0804
PackageArch	s390x
PackageDescription	Valgrind 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.
PackageName	valgrind
PackageRelease	293.d_t.2
PackageVersion	3.18.1
SHA-1	3F855EDD6B151667AA9F215C41AFB25CA3379FD9
SHA-256	EDD27D865D4FFFE891A6A0A0C0B560CB6BC7A28261967D91DA8F337426D58F9F

Key	Value
MD5	3DBED4B2C5F379EBE00878ABA1112724
PackageArch	s390x
PackageDescription	Valgrind 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.
PackageName	valgrind
PackageRelease	293.d_t.1
PackageVersion	3.18.1
SHA-1	449F8FCCEE5DFF0F7F7D3CD85D5DE5D6F2FE8064
SHA-256	0DE1FBF348CD0C5F0856FD403D08F19169EFED62A647BE061FB809F552FC0D88

Key	Value
MD5	C9CF7FAE2E3F3E4C1565DF54DC6BFF5D
PackageArch	x86_64
PackageDescription	Valgrind 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.
PackageName	valgrind
PackageRelease	293.d_t.2
PackageVersion	3.18.1
SHA-1	502A32353919F92FE61B5C9EA1F69F84ACFA8868
SHA-256	09B3D8DD98170218F8F15122A9649D34CE9637D58150183F606D2FB22FCE2F92

Key	Value
MD5	F22DD25262B9301185E5EDA9F9A2DEAD
PackageArch	s390x
PackageDescription	Valgrind 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.
PackageMaintainer	https://www.suse.com/
PackageName	valgrind
PackageRelease	293.d_t.1
PackageVersion	3.18.1
SHA-1	664D5777F53D2AF87CBE3C99644CA5E7C12BB0F3
SHA-256	A547A30C71C3A31AAC4DDDCB61741B388F93EAD7E1D306BAC906C2FC7513DFD1